Compiled HTML Help is a Microsoft help file format that can be abused as a malware container or execution vehicle. In threat campaigns, CHM files are attractive because they can run script-like content, may appear benign to users, and can bypass some controls that focus on office documents.
What Compiled HTML Help Is Used For
Compiled HTML Help, or CHM, is a Microsoft help file format that can carry more than static documentation. In abuse cases, it becomes a convenient container for script-like content and a delivery format that can look ordinary to users while still supporting malicious behaviour.
The security issue is not the file extension alone, but the trust a help file can inherit from its appearance and context. That makes CHM useful in social engineering, initial execution chains, and staged malware delivery, especially when users expect documentation or product support material.
Why CHM Files Are Attractive to Attackers
CHM files can be opened as if they were legitimate support content, which helps them blend into email attachments, downloads, and software-related lures. Their structure can hide active content inside something many people associate with harmless help pages.
Attackers value that mismatch between appearance and behaviour. A file that looks like documentation may still trigger code execution, follow-on payload retrieval, or local system interaction, which makes CHM a useful step in a broader malware chain rather than just a simple attachment format.
CHM abuse also benefits from uneven security coverage. Some controls that concentrate on office documents, macro-enabled files, or obvious executable formats may not treat help files with the same suspicion, so CHM can slip through policy, user awareness, or file-handling assumptions.
How CHM Abuse Fits Into Malware Delivery
In threat campaigns, CHM is often one link in a sequence rather than the final payload. A help file may be used to present a lure, launch script-like logic, or redirect the user into another malicious component while keeping the initial interaction low-friction.
This pattern matters because execution can happen through a trusted-looking user action, not only through obvious malware execution. Once opened, the file may initiate code paths that are harder to spot in casual review than a conventional executable or macro document.
That makes CHM relevant to defenders who model attack chains, not just file types. If the initial object looks benign, security teams may miss the fact that it is functioning as an execution vehicle, a staging wrapper, or a disguise for further malicious activity.
Defensive Handling and Review
CHM should be handled as an active content format, not as passive documentation by default. Filtering, detonation, or file-type policy should account for the fact that help files can contain behaviour that is materially different from plain text or static HTML.
For investigation, the important question is whether the file is being used as a delivery container, a user lure, or a mechanism for launching additional content. That means examining the source of the file, the context in which it was received, and any child activity associated with opening it.
When defenders review suspicious CHM activity, they should look at process creation, script execution, downloads triggered after opening, and any attempt to blend into legitimate help or support workflows. The goal is to separate normal documentation use from malicious packaging or execution.
Risk and Threat Considerations
CHM files are risky because they combine a trusted-looking presentation with the potential for executable or script-like behaviour. That makes them useful for bypassing user suspicion and for slipping past controls that are tuned to more familiar attachment types.
Failure mechanism: The file is opened as if it were help content, but embedded behaviour or linked activity produces code execution, payload staging, or other malicious follow-on actions.
Impact: The result can be initial compromise, malware deployment, and a deceptive entry point that is harder to spot in both user review and security monitoring.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1204 — User Execution | CHM abuse depends on user opening a crafted file to trigger malicious behaviour. |
| Recommendation — Map CHM delivery chains to User Execution and monitor for suspicious file-open activity. | ||
| NIST SP 800-53 Rev 5 | SI-3 — Malicious Code Protection | CHM can function as a malware container or execution vehicle needing content inspection and blocking. |
| Recommendation — Apply SI-3 to inspect and block risky CHM content before execution. | ||
| CIS Controls v8 | CIS-10 — Malware Defenses | CHM abuse is a malware delivery problem that benefits from filtering and execution controls. |
| Recommendation — Use malware defenses to quarantine suspicious CHM files and reduce execution risk. | ||
Practitioner Guidance
What to watch for: Treat CHM as a potentially executable delivery format when it arrives by email, download, or support-channel workflow. A benign-looking help file that is unexpected, unsolicited, or inconsistent with the sender’s normal behaviour deserves closer scrutiny.
Governance implication: Security policy should classify CHM alongside other risky container formats, with clear handling rules for quarantine, inspection, and user awareness. The practical lesson is to judge the file by its behaviour and provenance, not by the assumption that “help file” means safe.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org