Suspicious __init__.py Drop in Public Directory by Slow Pisces (via file_event)

PremiumReviewedSigma · Medium · v1
Product
macos
Category
file_event
Author
HuntRule
Published
2026-10-18
Updated
2026-10-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 creation of an __init__.py file inside the user Public directory, the drop location used by Slow Pisces to stage its RN Loader Python payload during fake coding-challenge lures. Planting a Python package init file in this path enables execution of the malicious loader when the developer runs the challenge code.

Related detections9 linkedT1204.002 — drag to rearrange
Linux process execution indicators for TanStack preinstall supply-chain payloads
Windows AppLocker Audit-Mode Events Indicate Files Would Have Been Blocked
Windows AppLocker Blocked Application, Script, MSI, or Packaged-App Execution
Malicious Script Execution via Cisco AnyConnect OnConnect Handler Abuse
Suspicious mshta Launched from Explorer via ClickFix Run Dialog (via process_creation)
Suspicious npm Package Spawning cURL Download via Process Creation
Suspicious curl Download Launched from PDF Shortcut Lure (via process_creation)
Malicious CivilDefense Loader Spawning civildefensestarter Payload (via process_creation)
Malicious Python Reverse Shell One-Liner Execution (via process_creation)
Suspicious __init__.py Drop in Public Directory by Slow Pisces (via file_event)
Pivot detection · T1204.002 · 9 related

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