Suspicious Python Loader Execution from Public Directory

ATT&CK techniques

Execution

Recon
Resource Dev
Initial Access
Execution
- T1059.006Python
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
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.

Reporting behind it

Related detections9 linkedT1059.006 — drag to rearrange

Suspicious Python Executing Staged Script From Temp Directory via DPRK Pyperclip Loader

Suspicious KANDYKORN Python Loader Execution via Process Creation

Suspicious Wscript Spawning Embedded Python Interpreter (via process_creation)

Suspicious Child Process Spawned by Python Interpreter via Process Creation

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 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.

Full detection rule

Unlock this rule to view and copy it

The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.

Sign in for 3 free unlocks

Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.

Also included

Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.

See it run on a free rule →Convert your own rule →