Suspicious Obfuscated Batch Execution via Legacy Command Interpreter (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-10-04
Updated
2026-10-04

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 the legacy command.com interpreter spawning cmd.exe to run a batch file from a user-writable directory, a pattern used by CypherIT-packed Lumma loaders. The obfuscated batch stage unpacks and launches the stealer while evading naive command-line inspection.

Related detections9 linkedT1059.003 — drag to rearrange
Suspicious Executable Launched From AppData Roaming Linked to GootLoader
Suspicious Batch Script Execution From Temp via Command Interpreter Linked to GootLoader
Suspicious Execution of Log File via cmd.exe (via process_creation)
Malicious ClickFix Execution via Headless Conhost
Suspicious Command Shell Spawned by MSSQL Server Process
Suspicious Named Pipe Creation via Command Echo
Exchange Worker Process Spawning Command Shell via OWASSRF
Suspicious Command Execution via ComSpec Environment Variable Obfuscation
Suspicious File Concatenation via copy Binary Mode
Suspicious Obfuscated Batch Execution via Legacy Command Interpreter (via process_creation)
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.