Techniques › T1137.005 › AN0263
AN0263 Analytic 0263
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Adversary uses a tool like Ruler or MFCMapi to create a malicious Outlook rule that triggers execution upon receipt of a crafted email. On email delivery, Outlook executes the rule, resulting in code execution (e.g., launching mshta.exe or PowerShell). Outlook spawns a non-standard child process, often unsanctioned, without user interaction.</p>
- Detects
- T1137.005 Outlook Rules
- Part of
- DET0095 Detect Persistence via Malicious Outlook Rules
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| WinEventLog:Sysmon | EventCode=1 | DC0032 Process Creation |
| WinEventLog:Sysmon | EventCode=7 | DC0016 Module Load |
| WinEventLog:Application | Outlook rule execution failure or abnormal rule execution context | DC0038 Application Log Content |
| WinEventLog:PowerShell | PowerShell launched from outlook.exe or triggered without user invocation | DC0064 Command Execution |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
ChildProcessName | Outlook may spawn mshta.exe, powershell.exe, or wscript.exe depending on attacker payload |
RuleTriggerCondition | Rule execution may depend on message subject, sender, or message header content |
ParentProcessName | Legitimate Outlook activity should not spawn scripting or interpreter processes |
TimeWindow | Execution may occur with delay after message receipt or folder interaction |