Suspicious Office Application Spawning Script Interpreter Chain

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

ATT&CK techniques

Execution
  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. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects Microsoft Word spawning a command shell or PowerShell that in turn is associated with script-host execution, a chain observed in a WizardSpider-themed intrusion where winword launched cmd or PowerShell leading to cscript. It captures the transition from a weaponized document to interactive command execution. Detecting this parent-child relationship is important because productivity applications launching shells is a strong indicator of malicious macro or exploit activity.

Related detections9 linkedT1059.003 — drag to rearrange
Windows Process Tree for Axios npm Supply-Chain RAT Droppers (cscript, curl, PowerShell)
Windows AppLocker Audit-Mode Events Indicate Files Would Have Been Blocked
Windows AppLocker Blocked Application, Script, MSI, or Packaged-App Execution
Windows Process Creation: Suspicious Children Spawned by HTML Help (hh.exe)
Windows: Alert on Suspicious HH.EXE Process Execution
Windows: Koadic Command Prompt Invocation with /q /c chcp
Suspicious Rename of Text File to Script via Move Command
Malicious RoKRAT Staged Loader Files in Temp via LNK (via file_event)
Malicious Command Execution Spawned by SharePoint w3wp Worker Process
Suspicious Office Application Spawning Script Interpreter Chain
Pivot detection · T1059.003 · 9 related

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