Suspicious Execution of Log File via cmd.exe (via process_creation)

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

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 WailingCrab decoding its payload into a log file in the Temp directory and executing it through cmd.exe, which treats the file as a batch script. Command interpreters invoking a log file are highly unusual on normal systems. This pattern reveals the staged payload launch.

Related detections9 linkedT1059.003 — drag to rearrange
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 Hidden PowerShell Launched by Batch Script
Suspicious Command Shell Executing Batch Script from LNK Delivery
Suspicious Office Application Spawning Script Interpreter Chain
Suspicious Execution of Log File via cmd.exe (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.