Detect Email Forwarding Rule in Sumo Logic CSE
Adversaries may set up email forwarding rules to covertly collect and monitor victim email communications. By creating inbox rules, mailbox-level SMTP forwarding configurations, or Exchange transport rules, adversaries can silently redirect all or targeted messages to attacker-controlled accounts — internal or external — without the victim's awareness. This technique provides persistent intelligence access even after compromised credentials are reset, because forwarding rules survive password changes. Adversaries may also use the Microsoft Messaging API (MAPI) to create hidden inbox rules not visible through Outlook, OWA, or standard Exchange administration tools, enabling long-term covert collection. Threat groups including LAPSUS$, Scattered Spider, Kimsuky, Star Blizzard, and Silent Librarian have actively abused this technique. LAPSUS$ notably created tenant-level Exchange transport rules to forward all organizational email to newly created attacker-controlled accounts, achieving org-wide collection with a single rule.
MITRE ATT&CK
- Tactic
- Collection
- Technique
- T1114 Email Collection
- Sub-technique
- T1114.003 Email Forwarding Rule
- Canonical reference
- https://attack.mitre.org/techniques/T1114/003/
Sumo Detection Query
_sourceCategory="o365" OR _sourceCategory="microsoft/o365"
| json field=_raw "Workload" as workload
| json field=_raw "Operation" as operation
| json field=_raw "UserId" as user_id
| json field=_raw "ClientIP" as client_ip
| json field=_raw "ObjectId" as affected_mailbox
| where workload = "Exchange"
| where operation in ("New-InboxRule","Set-InboxRule","Enable-InboxRule",
"New-TransportRule","Set-TransportRule","Enable-TransportRule",
"Set-Mailbox")
| json field=_raw "Parameters" as params_array
| parse regex field=params_array "\{\"Name\":\"(?<param_name>[^\"]+)\",\"Value\":\"(?<param_value>[^\"]+)\"\}" multi
| where param_name in ("ForwardTo","ForwardAsAttachmentTo","RedirectTo",
"ForwardingSmtpAddress","ForwardingAddress",
"DeliverToMailboxAndForward","RedirectMessageTo","BlindCopyTo")
| where param_value != "" and param_value != "False" and param_value != "false" and param_value != "null"
| if (param_value matches "*@*" and !(param_value matches "*onmicrosoft.com*"), 1, 0) as is_external
| if (operation matches "*TransportRule*", 1, 0) as is_transport_rule
| if (_raw matches "*HideRule*" or _raw matches "*Hidden*", 1, 0) as hidden_rule
| (is_external * 2) + (is_transport_rule * 3) + (hidden_rule * 3) + 1 as severity_score
| fields _messageTime, user_id, client_ip, operation, param_name, param_value, affected_mailbox, is_external, is_transport_rule, hidden_rule, severity_score
| sort by severity_score, _messageTime descSumo Logic query detecting Microsoft 365 Exchange email forwarding rule abuse. Parses O365 management activity logs to identify inbox rule, transport rule, and mailbox forwarding operations, with scoring for external targets, tenant-wide transport rules, and hidden rule configurations consistent with T1114.003.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate email archiving or compliance solutions (e.g., Veeam, AvePoint) that configure mailbox-level forwarding to journal mailboxes
- HR or legal teams setting up monitored mailbox forwarding for employee investigations with proper authorization and documentation
- Shared mailbox management where admins configure forwarding to team distribution lists for business continuity
Other platforms for T1114.003
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Create Inbox Forwarding Rule via Exchange Online PowerShell
Expected signal: OfficeActivity (Sentinel) and o365:management:activity (Splunk): Operation=New-InboxRule, [email protected], [email protected], Parameters array contains {Name:ForwardTo, Value:[email protected]}. Event appears in Unified Audit Log within 15-60 minutes. Azure AD Sign-In Logs will record the Exchange Online session from the admin account.
- Test 2Set Mailbox-Level SMTP Forwarding via Set-Mailbox
Expected signal: OfficeActivity: Operation=Set-Mailbox, Parameters array contains {Name:ForwardingSmtpAddress, Value:[email protected]} and {Name:DeliverToMailboxAndForward, Value:True}. This forwarding is NOT visible via Get-InboxRule — only via Get-Mailbox -Identity victim | fl ForwardingSmtpAddress, ForwardingAddress, DeliverToMailboxAndForward.
- Test 3Create Org-Wide Transport Rule to Blind-Copy All Mail (LAPSUS$ Pattern)
Expected signal: OfficeActivity: Operation=New-TransportRule, [email protected], Parameters contains {Name:BlindCopyTo, Value:[email protected]} and {Name:FromScope, Value:InOrganization}. This is NOT logged to individual mailbox audit logs — only appears in Exchange Admin Audit Log and the Unified Audit Log at the tenant level. Transport rule changes take effect within minutes.
- Test 4Bulk Enumerate All Mailbox Forwarding Configurations (Reconnaissance Phase)
Expected signal: OfficeActivity: Multiple Operation=Get-InboxRule events from admin account accessing many mailboxes in rapid succession. High-volume Exchange admin read operations within a short time window generate multiple OfficeActivity records. Azure AD Sign-In Logs record the session. This pattern can be detected with anomaly-based analytics on Exchange admin read volume.
References (10)
- https://attack.mitre.org/techniques/T1114/003/
- https://blog.compass-security.com/2018/09/hidden-inbox-rules-in-microsoft-exchange/
- https://blogs.technet.microsoft.com/timmcmic/2015/06/08/exchange-and-office-365-mail-forwarding-2/
- https://learn.microsoft.com/en-us/exchange/security-and-compliance/mail-flow-rules/mail-flow-rules
- https://www.us-cert.gov/ncas/alerts/TA18-086A
- https://www.microsoft.com/en-us/security/blog/2022/03/22/dev-0537-criminal-actor-targeting-organizations-for-data-exfiltration-and-destruction/
- https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/external-email-forwarding
- https://github.com/sensepost/ruler
- https://learn.microsoft.com/en-us/powershell/module/exchange/new-inboxrule
- https://learn.microsoft.com/en-us/powershell/module/exchange/new-transportrule
Unlock Pro Content
Get the full detection package for T1114.003 including response playbook, investigation guide, and atomic red team tests.