Malicious Office Application Spawning Script Interpreter

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-11-03
Updated
2026-11-03

ATT&CK techniques

Initial Access → Execution
  1. Recon

  2. Resource Dev

  3. Persistence

  4. Priv Esc

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects a Microsoft Office application such as Word or Excel spawning a command shell or scripting interpreter. In the WithSecure Initial Access Lab 1 a malicious macro launches powershell, cmd or wscript to execute the next stage. This parent-child relationship is a strong indicator of macro-based initial access from a phishing document.

Related detections9 linkedT1204.002 — drag to rearrange
Suspicious Office Application Spawning Script Interpreter
Suspicious DLL Written to Explorer IconCache Path
Ursnif C2 Proxy Traffic Identified by Base64 URI Encoding and .avi/.images Pattern
Windows process creation: Winword launching FLTLDR.exe exploitation behavior
Windows Process Creation: EQNEDT32.EXE Used as CVE-2017-11882 Exploit Dropper Parent
Windows: Winword spawning csc.exe indicative of CVE-2017-8759 exploitation
Suspicious Office Application Spawning Script Interpreter
Suspicious Executable Launched From ProgramData Root via Image Path (via process_creation)
Suspicious Office Application Spawning Regsvr32 via Process Chain (via process_creation)
Malicious Office Application Spawning Script Interpreter
Pivot detection · T1204.002 · 9 related

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