<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Winnti - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/actors/winnti/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 12 Oct 2026 18:24:40 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/actors/winnti/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Abuse of Compiled HTML Help Application for Decompilation</title><link>https://feed.craftedsignal.io/briefs/2026-10-hh-decompile-abuse/</link><pubDate>Mon, 12 Oct 2026 18:24:40 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-hh-decompile-abuse/</guid><description>Threat actors, including APT41, abuse the native Windows HTML Help application (hh.exe) to decompile CHM files for staging malicious payloads or bypassing security controls.</description><content:encoded><![CDATA[<p>The Microsoft HTML Help application (hh.exe) is a legitimate system binary that can be abused by attackers to perform unauthorized actions. By invoking the decompile parameter, an attacker can extract the contents of a Compiled HTML Help (.chm) file to a specified directory. This technique, documented as T1218.001, is often used as a proxy for execution or to unpack malicious payloads staged within seemingly benign help files. APT41 and other actors have historically utilized this mechanism to evade detection by leveraging a trusted, signed Windows binary to facilitate the delivery of secondary malware or configuration files. Defenders should prioritize monitoring for the infrequent use of the decompile switch in their endpoint environments.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker crafts or obtains a malicious CHM file containing secondary payloads or scripts.</li>
<li>The malicious file is delivered to the target host via phishing or web download.</li>
<li>The attacker executes hh.exe via a command-line interface or script.</li>
<li>The command utilizes the -decompile flag: hh.exe -decompile &lt;output_dir&gt; &lt;chm_file&gt;.</li>
<li>The contents of the CHM are extracted to the filesystem.</li>
<li>The extracted payloads, often scripts or binaries, are executed to achieve the primary goal, such as establishing C2 or persistence.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful abuse of this technique can allow attackers to bypass security restrictions by using a trusted system utility to drop malicious files. This facilitates further system compromise, persistence, and potential data exfiltration. While specific victim counts are not cited in current reports, the technique is a known component in the toolsets of advanced persistent threat groups.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Deploy detection coverage for the command-line usage of hh.exe with the decompile parameter.</p>
<ul>
<li>Implement the provided Sigma rule to alert on suspicious process creation events.</li>
<li>Enable Sysmon or EDR process-creation logging to capture full command-line arguments.</li>
<li>Audit the use of CHM files within the environment to identify unexpected help file execution.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">threat</category><category>living-off-the-land</category><category>defense-evasion</category><category>windows</category><category>endpoint</category></item></channel></rss>