<?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 365 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/microsoft-365/</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-365/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>Detection of Command and Control Activity via Commonly Abused Web Services</title><link>https://feed.craftedsignal.io/briefs/2024-01-04-c2-web-services/</link><pubDate>Thu, 04 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-04-c2-web-services/</guid><description>This rule detects command and control activity using common web services by identifying Windows hosts making DNS requests to a list of commonly abused web services from processes outside of known program locations, potentially indicating adversaries attempting to blend malicious traffic with legitimate network activity.</description><content:encoded><![CDATA[<p>Adversaries may implement command and control (C2) communications that use common web services to hide their activity. This attack technique is typically targeted at an organization and uses web services common to the victim network, which allows the adversary to blend into legitimate traffic activity. These popular services are typically targeted since they have most likely been used before compromise, which helps malicious traffic blend in. This detection focuses on identifying connections from Windows hosts to a predefined list of commonly abused web services from processes running outside of typical program installation directories, indicating a potential C2 channel leveraging legitimate services. The rule aims to detect this behavior by monitoring network connections and DNS requests originating from unusual locations.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial access is achieved via an unknown method (e.g., phishing, exploit).</li>
<li>Malware is installed on the victim&rsquo;s system, likely outside typical program directories.</li>
<li>The malware establishes a DNS connection to a commonly abused web service (e.g., pastebin.com, raw.githubusercontent.com) to obscure C2 traffic.</li>
<li>The malware sends encrypted or encoded commands to the web service.</li>
<li>The web service acts as an intermediary, relaying the commands to the attacker&rsquo;s C2 server.</li>
<li>The C2 server responds with instructions, which are then relayed back to the compromised host through the same web service.</li>
<li>The malware executes the received commands, potentially leading to data exfiltration, lateral movement, or other malicious activities.</li>
<li>The attacker maintains persistent access and control over the compromised system using the web service as a hidden C2 channel.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation can lead to data theft, system compromise, and further propagation within the network. Since commonly used web services are utilized, the malicious activity can blend in with legitimate network traffic, making it difficult to detect. The impact can range from minor data breaches to complete network compromise, depending on the attacker&rsquo;s objectives and the level of access gained.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Detect Commonly Abused Web Services via DNS</code> to your SIEM to identify suspicious DNS queries to known C2 web services originating from anomalous processes.</li>
<li>Enable DNS query logging on Windows endpoints to provide the data source required for the Sigma rule.</li>
<li>Review network connection logs for processes outside standard installation directories communicating with domains listed in the <code>query</code> section of the Sigma rule to identify potential C2 activity.</li>
<li>Implement network segmentation to limit the potential impact of compromised hosts.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>command-and-control</category><category>windows</category><category>threat-detection</category></item><item><title>Microsoft 365 Suspicious Email Delivery</title><link>https://feed.craftedsignal.io/briefs/2024-01-m365-suspicious-email/</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-m365-suspicious-email/</guid><description>This brief outlines a threat where Microsoft Defender for Office 365 identifies an email as malicious or suspicious but still delivers it to a user's inbox or junk folder, potentially bypassing initial security measures.</description><content:encoded><![CDATA[<p>This threat involves malicious or suspicious emails, as identified by Microsoft Defender for Office 365, being delivered to user mailboxes despite the existing security mechanisms. This can occur due to various factors, including misconfigured security policies, sophisticated attacker techniques that evade detection, or delayed signature updates. The delivery of such emails presents a significant risk, as they may contain spearphishing attachments, malicious links, or other harmful content designed to compromise user accounts or systems. Successful exploitation can lead to data theft, malware infection, and further propagation of the attack within the organization. It&rsquo;s crucial to investigate these instances promptly to remediate any potential damage and improve email security posture.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker crafts a spearphishing email designed to bypass standard security filters.</li>
<li>The email is sent to a target user within the Microsoft 365 environment.</li>
<li>Microsoft Defender for Office 365 analyzes the email and identifies it as suspicious but fails to block delivery.</li>
<li>The email is delivered to the user&rsquo;s Inbox or Junk folder.</li>
<li>The user opens the email and clicks on a malicious link or opens a malicious attachment (e.g., a macro-enabled document).</li>
<li>The link redirects the user to a credential harvesting site, or the attachment executes malicious code (e.g., via PowerShell).</li>
<li>The attacker gains access to the user&rsquo;s account or system.</li>
<li>The attacker uses the compromised account to further propagate the attack, exfiltrate data, or deploy malware within the organization.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The impact of this threat can be significant. Successful exploitation can lead to the compromise of user accounts, data theft, malware infection, and financial loss. Organizations may experience business disruption, reputational damage, and legal liabilities. The number of affected users and the extent of the damage will depend on the attacker&rsquo;s objectives and the organization&rsquo;s security controls.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule provided to detect suspicious email delivery events within your Microsoft 365 environment and tune for your specific environment.</li>
<li>Investigate any alerts generated by the Sigma rule to determine the root cause of the bypass and remediate any potential damage.</li>
<li>Review and adjust Microsoft Defender for Office 365 settings to improve detection accuracy and blocking capabilities.</li>
<li>Educate users about the risks of phishing emails and encourage them to report suspicious messages.</li>
<li>Monitor the <code>TIMailData</code> operation within the M365 audit logs for further analysis and threat hunting.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>suspicious-email</category><category>phishing</category><category>microsoft365</category></item></channel></rss>