Windows Process Creation: Exchange PowerShell Snap-in Loading via Add-PSSnapin

Flags PowerShell executions that Add-PSSnapin Exchange snap-ins, consistent with Exchange mailbox/config data collection.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
FPT.EagleEye, Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-03-03
Updated
2026-07-30

ATT&CK techniques

Execution → Collection
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule identifies PowerShell or pwsh process execution where the command line includes Add-PSSnapin and targets Exchange PowerShell snap-in modules. Attackers may use snap-ins to interact with Exchange functionality for mailbox or configuration data collection. Telemetry relies on Windows process creation events capturing the image name and command line, including optional checks to exclude an msiexec parent process scenario.

Related detections9 linkedT1059.001 — drag to rearrange
Malicious Interlock RAT FileFix Download-Cradle via PowerShell WebClient with PowerShell User-Agent (via ps_script)
Malicious Metasploit Stager Delivery via mshta Remote HTA (via process_creation)
Suspicious PowerShell Download of Disguised Payload to ProgramData
Suspicious PowerShell WebClient Download of Executable Payload
Malicious Script Host Spawning PowerShell in Gootloader Chain
Suspicious PsExec Service Launching Encoded PowerShell Payload
Suspicious PowerShell Remote Script Execution via IEX DownloadString
Malicious SharePoint ToolShell Post-Exploitation via Encoded PowerShell (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Windows Process Creation: Exchange PowerShell Snap-in Loading via Add-PSSnapin
Pivot detection · T1059.001 · 9 related

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