<?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/"><channel><title>Microsoft Windows — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/microsoft-windows/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 30 Apr 2026 13:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/microsoft-windows/feed.xml" rel="self" type="application/rss+xml"/><item><title>ClickFix 'BackgroundFix' Campaign Delivers CastleLoader, NetSupport RAT, and CastleStealer</title><link>https://feed.craftedsignal.io/briefs/2026-04-clickfix-backgroundfix/</link><pubDate>Thu, 30 Apr 2026 13:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-clickfix-backgroundfix/</guid><description>The 'BackgroundFix' ClickFix campaign uses social engineering to trick victims into downloading malware disguised as a free image-editing tool, leading to the deployment of CastleLoader, NetSupport RAT for remote access, and CastleStealer for credential theft.</description><content:encoded><![CDATA[<p>The BackgroundFix campaign is a social engineering scheme using fake &ldquo;remove your photo background&rdquo; services to deliver malware. Victims are lured to malicious sites mimicking legitimate image editing tools. The sites feature fake upload interfaces, progress bars, and download buttons to appear authentic. This campaign delivers a multi-stage payload, starting with CastleLoader. CastleLoader then drops NetSupport RAT, enabling remote access for the attackers, and CastleStealer, a custom .NET stealer designed to exfiltrate browser credentials, wallet extension data, and Telegram session files. This campaign appears to be active, with multiple domains sharing the same template.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Victim searches for an online background removal tool and lands on a malicious BackgroundFix site.</li>
<li>The victim uploads an image to the fake website.</li>
<li>After clicking a checkbox, the site instructs the victim to copy a command to their clipboard.</li>
<li>The copied command executes <code>finger.exe</code> to query <code>cheeshomireciple[.]com</code></li>
<li><code>finger.exe</code> retrieves a batch script from the C2 server.</li>
<li>The batch script executes commands to download and execute further payloads.</li>
<li>CastleLoader is deployed, subsequently dropping NetSupport RAT and CastleStealer.</li>
<li>NetSupport RAT grants the attacker remote access, while CastleStealer exfiltrates sensitive data.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful attacks result in the installation of NetSupport RAT, granting attackers remote control over the compromised system. Additionally, CastleStealer exfiltrates sensitive information such as browser credentials, wallet extension data, and Telegram session files. This stolen data can be used for further malicious activities, including financial fraud, identity theft, and unauthorized access to sensitive accounts. The active nature of the campaign and the use of multiple domains suggest a broad targeting scope.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor process creation events for the execution of <code>finger.exe</code> with command-line arguments pointing to external domains (IOC: <code>cheeshomireciple[.]com</code>).</li>
<li>Deploy the Sigma rule to detect the execution of <code>finger.exe</code> to identify potential initial access attempts.</li>
<li>Block the C2 domain <code>cheeshomireciple[.]com</code> at the DNS resolver to prevent initial payload delivery.</li>
<li>Monitor network connections for NetSupport RAT C2 communications on port 688 to detect compromised systems (IOCs: <code>poronto[.]com:688</code>, <code>giovettiadv[.]com:688</code>).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>clickfix</category><category>malware</category><category>social-engineering</category><category>rat</category><category>infostealer</category><category>castleloader</category><category>netsupport</category></item><item><title>Registry Persistence via AppInit DLL Modification</title><link>https://feed.craftedsignal.io/briefs/2024-01-appinit-dll-persistence/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-appinit-dll-persistence/</guid><description>Modification of the AppInit DLLs registry keys on Windows systems allows attackers to execute code in every process that loads user32.dll, establishing persistence and potentially escalating privileges.</description><content:encoded><![CDATA[<p>The AppInit DLLs mechanism allows dynamic-link libraries (DLLs) to be loaded into every process that creates a user interface (loads user32.dll) on Microsoft Windows operating systems. This mechanism is intended for customization of the user interface and behavior of Windows-based applications. However, attackers can abuse this by adding malicious DLLs to the registry locations associated with AppInit DLLs. This enables them to execute code with elevated privileges, similar to process injection, and maintain a persistent presence on the compromised machine. This technique is often used to maintain access after initial compromise. Detection focuses on registry modifications to the relevant keys, excluding known legitimate processes to minimize false positives. The referenced Elastic rule was last updated on 2026/05/04.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to the system through a vulnerability, phishing, or other means.</li>
<li>The attacker identifies the AppInit DLLs registry keys: <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows</code> or <code>HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows</code>.</li>
<li>The attacker modifies the <code>AppInit_DLLs</code> registry value to include the path to their malicious DLL.</li>
<li>The attacker&rsquo;s DLL is placed on the filesystem, typically in a location where it will persist across reboots.</li>
<li>Any new process that loads user32.dll will automatically load the attacker&rsquo;s malicious DLL.</li>
<li>The malicious DLL executes arbitrary code within the context of the newly created process.</li>
<li>The attacker can use this code execution to perform further actions, such as installing backdoors or escalating privileges.</li>
<li>The attacker maintains persistent access to the system through the malicious DLL loaded into every user interface process.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows attackers to execute arbitrary code within the context of any process that loads <code>user32.dll</code>. This provides a persistent mechanism for maintaining access to the compromised system. The attacker gains code execution with elevated privileges, similar to process injection. This can lead to data theft, system compromise, or further lateral movement within the network. While no specific victim counts are mentioned, the widespread use of Windows makes this a potentially high-impact vulnerability.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor registry modifications to the <code>AppInit_DLLs</code> value in <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows</code> and <code>HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows</code> using the &ldquo;Registry Persistence via AppInit DLL Modification&rdquo; Sigma rule.</li>
<li>Enable Sysmon registry event logging to provide the data required for the Sigma rule to function correctly.</li>
<li>Deploy the &ldquo;Registry Persistence via AppInit DLL Modification&rdquo; Sigma rule to your SIEM and tune the filter to exclude known-good DLL paths in your environment.</li>
<li>Investigate any alerts triggered by the Sigma rule, focusing on the parent process and the DLL being loaded.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>persistence</category><category>defense-evasion</category><category>appinit-dlls</category><category>registry</category><category>windows</category></item></channel></rss>