Malicious Python Execution from Hidden .pyp Directory in Lazarus InvisibleFerret Chain (via process_creation)

ATT&CK techniques

Execution

Recon
Resource Dev
Initial Access
Execution
- T1059.007JavaScript
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule detects the Python interpreter running from a hidden .pyp folder inside a user profile, the staging location used by the Lazarus BeaverTail and InvisibleFerret campaign to launch its backdoor and stealer components. The dot-prefixed directory hides a private Python runtime that then executes payloads such as the .sysinfo module. Running python from such a concealed per-user path is not legitimate.

Reporting behind it

Related detections9 linkedT1059.007 — drag to rearrange

Suspicious Script Host Launching PowerShell from Fattura Named JScript File (via process_creation)

Suspicious Double-Extension PDF JavaScript Lure via WScript (via process_creation)

Suspicious Script Host Spawning PowerShell from Fake Browser Update JS

Suspicious MMC Console Spawning Script Interpreter via GrimResource

Suspicious Script Host Spawning PowerShell via Process Creation

Malicious Node.js Execution of Hidden .claude Setup Script

Suspicious PowerShell Spawned by cscript in Script Chain

Suspicious npm Postinstall Node Execution From Fixtures Path (BeaverTail OtterCookie)

Suspicious Script Host Execution of Decoy-Named JavaScript Dropper (PS1Bot)

Malicious Python Execution from Hidden .pyp Directory in Lazarus InvisibleFerret Chain (via process_creation)

Pivot detection · T1059.007 · 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 →