Chm - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/chm/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 03 Jan 2024 12:00:00 +0000HTML Help Executable Spawning Child Processeshttps://feed.craftedsignal.io/briefs/2024-01-html-help-spawn/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-html-help-spawn/The execution of hh.exe (HTML Help) spawning a child process indicates the use of a Compiled HTML Help (CHM) file to execute potentially malicious Windows script code.Attackers may abuse the HTML Help executable (hh.exe) to execute malicious code on a target system. Compiled HTML Help (CHM) files can contain embedded scripts or links to external resources. When a CHM file is opened, hh.exe renders the content, potentially triggering the execution of malicious scripts. This technique is often used to bypass security controls and deliver malware. This behavior is significant as it may indicate an attempt to execute malicious scripts via CHM files, a known technique for bypassing security controls. If confirmed malicious, this could lead to unauthorized code execution, potentially compromising the system. The LOLBAS project documents this use of hh.exe, and it has been observed in use by various threat actors.

Attack Chain

  1. An attacker crafts a malicious CHM file containing embedded scripts or links.
  2. The CHM file is delivered to the victim via email or other means.
  3. The victim opens the CHM file, which is processed by hh.exe.
  4. Hh.exe renders the HTML content within the CHM file.
  5. The embedded script (e.g., JavaScript, VBScript) or link is executed.
  6. The script spawns a child process (e.g., cmd.exe, powershell.exe) using ShellExecute or similar methods.
  7. The child process executes arbitrary commands, downloads malware, or performs other malicious actions.
  8. The attacker gains control of the system or exfiltrates data.

Impact

Successful exploitation of this technique can lead to arbitrary code execution, allowing the attacker to compromise the system. This can result in data theft, installation of malware, or further propagation within the network. The number of potential victims is broad, as CHM files can be distributed through various channels. The impact ranges from individual workstation compromise to widespread organizational breaches.

Recommendation

  • Monitor process creation events for hh.exe spawning child processes to detect potential malicious activity, as described in the overview.
  • Implement the Sigma rule Detect HTML Help Spawning CMD to identify instances of hh.exe spawning command interpreters.
  • Deploy the Sigma rule Detect HTML Help Spawning PowerShell to detect instances of hh.exe spawning PowerShell processes.
  • Enable Sysmon process creation logging to capture the necessary process execution data.
  • Block known malicious CHM files based on file hash (if available from threat intelligence feeds, although none are included here).
]]>highadvisoryhtml-helpchmlolbasprocess-creation