Malicious JADEPUFFER Python Beacon via Cron

ATT&CK techniques

Execution → C2

Recon
Resource Dev
Initial Access
Execution
- T1053.003Cron
Persistence
- T1053.003Cron
Priv Esc
- T1053.003Cron
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
- T1071Application Layer Protocol
Exfiltration
Impact

What it detects

This rule detects inline Python one-liners using urllib to contact a beacon endpoint, the scheduled command-and-control mechanism of the JADEPUFFER agentic ransomware for automated database extortion. The actor installs a cron entry that periodically calls back to its beacon path. This pattern indicates scheduled ransomware C2 activity.

Reporting behind it

Related detections9 linkedT1071 — drag to rearrange

Malicious Keyhunter Worker Persistence via Systemd Service

Suspicious Python Process Establishing PostgreSQL Command and Control Channel

Malicious Cron Execution of Binary from tmp Directory on Linux (via process_creation)

Possible WailingCrab MQTT C2 to Public Broker (via network_connection)

Suspicious Process Execution from Hidden Outlaw Config Directory

Suspicious Outbound Network Connection from explorer.exe

Suspicious Cron Reboot Persistence Pointing to Hidden User Directory on Linux

Suspicious SSH Service on Non Standard Port 57722

Suspicious Cron Job Downloading and Executing Payload via GlobalProtect Exploitation

Malicious JADEPUFFER Python Beacon via Cron

Pivot detection · T1071 · 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 →