Suspicious Node.js Spawning Python or Tar Interpreter

PremiumReviewedSigma · Low · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-26
Updated
2026-09-26

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 node.exe spawning python.exe or tar.exe which reflects the Lazarus loader chain where a malicious server.js executes downloaded Python payloads and unpacks archives. The behaviour extracts and runs second-stage InvisibleFerret and BeaverTail components. It is important because it reveals code execution smuggled through a seemingly benign development runtime.

Related detections9 linkedT1059.006 — drag to rearrange
Malicious Python Inline Base64 Reverse Shell Execution
Suspicious Python Reverse Shell One-Liner Execution via GlobalProtect Exploitation
Malicious Python Reverse Shell Execution on macOS
Suspicious Python Execution from Windows Store App Path
Possible Trojanised Python Native Extension Load of gradient Module
Malicious AI CLI Anti-Attribution and Permission Bypass Flags
Suspicious Python HTTP Server Staging for Payload Delivery
Suspicious Python Base64 Encoded Command Execution (via process_creation)
Suspicious __init__.py Drop in Public Directory by Slow Pisces (via file_event)
Suspicious Node.js Spawning Python or Tar Interpreter
Pivot detection · T1059.006 · 9 related

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