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
Suspicious Kimsuky Python Backdoor Staging in Winii Directory (via file_event)
SynkLoader Python Stager Execution from AppData via pythonw (via process_creation)
Malicious TeamPCP durabletask Payload python3 managed.pyz from tmp (via process_creation)
Suspicious Python Startup .pth File Creation for Interpreter Persistence
AteraAgent malicious installations
Suspicious Python Execution from WebDAV Share via PowerShell (via process_creation)
Malicious InvisibleFerret Python Loader Execution from Hidden .pyp Directory
Malicious Fileless Execution via memfd Anonymous File on Linux Cloud Workload (via process_creation)
Malicious TeamPCP LiteLLM .pth Startup Hook and Payload Dropper (via file_event)
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.