Windows Process Creation: Suspicious Children Spawned by mshta.exe

Flags mshta.exe spawning command, script, or utility processes commonly abused for executing malicious HTA payloads.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Michael Haag (SigmaHQ), DRL 1.1
Published
2019-01-16
Updated
2026-07-30

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies process creation events where the parent process is mshta.exe and the child process is one of several common command/script utilities (e.g., cmd.exe, PowerShell, wscript/cscript, bash/sh, reg.exe, regsvr32, bitsadmin). Attackers often abuse mshta.exe to execute malicious HTA content and then leverage these tools to run commands or stage payloads. The detection relies on Windows process creation telemetry, specifically parent image path endswith matching for mshta.exe and child image/original filename endswith or exact name matching.

Related detections9 linkedT1218.005 — drag to rearrange
Suspicious MSHTA Execution Spawned by Browser or Document Reader via Mispadu (via process_creation)
Suspicious Office Application Spawning Mshta With Remote HTA
Suspicious MSHTA VBScript WScript Shell Execution
Suspicious Remote HTA Payload Execution via MSHTA
Malicious Shell Spawned by Mshta Delivery (via process_creation)
Malicious Kimsuky Remote HTA Execution via URL Shortener (via process_creation)
ClickFix Paste-Jacking Execution of mshta Retrieving Remote Payload (via process_creation)
Suspicious mshta Execution of Remote HTA Payload
Suspicious Mshta Executed From Non-System Path (via process_creation)
Windows Process Creation: Suspicious Children Spawned by mshta.exe
Pivot detection · T1218.005 · 9 related

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