StealC Loader Execution via Blender Spawning Script Interpreter (via process_creation)

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-07-08
Updated
2026-08-28

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 blender.exe spawning a command shell or script interpreter such as PowerShell, cmd, or python, the execution behavior triggered when a malicious .blend file with embedded auto-run Python fetches a remote loader in the StealC V2 Blender campaign. Adversaries leverage the Blender Auto Run Python Scripts setting so opening a downloaded model executes their loader, making early detection critical for stopping the chain before the StealC stealer and Pyramid C2 module deploy.

Related detections9 linkedT1059.006 — drag to rearrange
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)
Malicious Python Reverse Shell One-Liner Execution (via process_creation)
Suspicious Silver Fox Backdoor Execution via pythonw appclient Module (via process_creation)
Suspicious Malicious MCP Package devtools-assistant Execution (via process_creation)
Malicious GitVenom Python Fernet Decrypt-and-Execute Loader via process_creation
Suspicious Python Executing Script from var root Library Caches on macOS (via process_creation)
StealC Loader Execution via Blender Spawning Script Interpreter (via process_creation)
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.