Suspicious Python Loader Execution from Public Directory

PremiumReviewedSigma · Medium · v1
Category
process_creation
Author
HuntRule
Published
2026-09-18
Updated
2026-09-18

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 a Python interpreter executing an __init__.py loader from a user Public directory, the staging pattern used in the DPRK Bit-By-Bit intrusion to run a malicious YAML deserialization payload. Python execution from a shared Public path is atypical and indicates malware staging and execution.

Related detections9 linkedT1059.006 — drag to rearrange
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)
Malicious Python Reverse Shell One-Liner Execution (via process_creation)
Suspicious Python Loader Execution from Public Directory
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.