Exchange Worker Process Spawning Command Shell via OWASSRF

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-28
Updated
2026-09-28

ATT&CK techniques

Initial Access → Persistence
  1. Recon

  2. Resource Dev

  3. Priv Esc

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects the IIS Exchange worker process w3wp.exe spawning cmd.exe or PowerShell, a hallmark of web-facing exploitation such as the OWASSRF Exchange remote code execution chain. Huntress observed base64-encoded PowerShell whoami commands launched this way for post-exploitation reconnaissance. Shell children of the Exchange worker almost always indicate a webshell or server-side request forgery exploit.

Related detections9 linkedT1190 — drag to rearrange
Malicious IIS Worker Process Spawning PowerShell via Gladinet CentreStack Exploit
MSSQL Server Process Spawning Command Shell via xp_cmdshell
Suspicious MSSQL xp_cmdshell OS Command Execution via sqlservr.exe (via process_creation)
Windows Process Creation: CrushFTP spawning PowerShell, CMD, and scripting tool execution
Windows: Suspicious child processes spawned by CrushFTP service
Windows Process Creation: Java exploitation chain targeting Zoho ManageEngine Desktop Central (CVE-2020-10189)
Suspicious PowerShell Out-of-Band Request to Interactsh Domain
Suspicious PowerShell Spawned by SysAid Java Process
Possible Ivanti EPMM In-Memory Java Webshell Access via mifs 403.jsp
Exchange Worker Process Spawning Command Shell via OWASSRF
Pivot detection · T1190 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.