<?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>Configuration_audit — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/configuration_audit/</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>Fri, 29 May 2026 13:29:13 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/configuration_audit/feed.xml" rel="self" type="application/rss+xml"/><item><title>M365 Exchange Inbox Forwarding Rule Created</title><link>https://feed.craftedsignal.io/briefs/2026-05-m365-exchange-inbox-rule/</link><pubDate>Fri, 29 May 2026 13:29:13 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-m365-exchange-inbox-rule/</guid><description>This rule detects the creation of new inbox forwarding rules in Microsoft 365, which can be abused by attackers to intercept and exfiltrate email data to external addresses.</description><content:encoded><![CDATA[<p>Attackers can abuse Microsoft 365 Exchange inbox rules to intercept and exfiltrate email data without making organization-wide configuration changes or having the corresponding privileges. This involves creating or modifying inbox rules to forward emails to externally controlled accounts. The detection rule focuses on successful events that specify forwarding parameters, thus identifying potential unauthorized email redirection activities. This activity is particularly concerning as it allows attackers to maintain persistence and access sensitive information without direct compromise of user credentials, blending in with legitimate administrative functions. A recent AI-enabled device code phishing campaign in April 2026 further highlights the importance of monitoring Exchange configurations for malicious rule creation.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial Access: An attacker gains initial access to a user&rsquo;s M365 account, possibly through phishing or credential stuffing.</li>
<li>Privilege Escalation (if needed): The attacker may attempt to escalate privileges within the compromised account or lateral movement to an account with appropriate permissions.</li>
<li>Rule Creation/Modification: The attacker uses Exchange PowerShell cmdlets like <code>New-InboxRule</code>, <code>Set-InboxRule</code>, <code>Set-Mailbox</code>, <code>Set-TransportRule</code>, or <code>New-TransportRule</code> to create a new inbox rule or modify an existing one.</li>
<li>Forwarding Configuration: The attacker configures the inbox rule to forward emails based on specific conditions to an external email address they control, using parameters such as <code>ForwardTo</code>, <code>ForwardAsAttachmentTo</code>, or <code>RedirectTo</code>.</li>
<li>Data Collection: Emails that meet the defined conditions are automatically forwarded to the attacker&rsquo;s external email address.</li>
<li>Data Exfiltration: The attacker collects sensitive information from the forwarded emails.</li>
<li>Persistence: The inbox rule remains active, providing ongoing access to email data as it arrives in the user&rsquo;s mailbox.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation can lead to the exfiltration of sensitive company information, including confidential documents, financial data, and customer information. This can result in financial loss, reputational damage, and legal liabilities. The number of victims and the extent of the damage depend on the scope of the compromised accounts and the sensitivity of the data being forwarded.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Detect M365 Exchange Inbox Rule Created to External Domain</code> to your SIEM and tune for your environment to identify suspicious forwarding rules.</li>
<li>Review the Microsoft 365 audit logs for events related to <code>New-InboxRule</code>, <code>Set-InboxRule</code>, <code>Set-Mailbox</code>, <code>Set-TransportRule</code>, and <code>New-TransportRule</code> where the forwarding address is external to the organization, as outlined in the rule description.</li>
<li>Implement multi-factor authentication (MFA) for all user accounts to reduce the risk of initial access via compromised credentials.</li>
<li>Regularly review and update email security policies to prevent unauthorized forwarding rules, as mentioned in the references.</li>
<li>Enable Sysmon process-creation logging to improve detection of malicious PowerShell activity, and investigate related detections.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>cloud</category><category>saas</category><category>email</category><category>microsoft_365</category><category>configuration_audit</category><category>email_collection</category></item></channel></rss>