Threat · curated 2 Jul 2026

JADEPUFFER: Agentic ransomware for automated database extortion

Dossier

Coverage timeline

2 Jul 2026thehackernews.comtheregister.comsysdig.comprimarybleepingcomputer.com+4 more

Why it matters

JadePuffer marks the first documented real-world intrusion where an AI agent autonomously executed a complete ransomware kill chain, signaling that agentic attackers can now adapt to obstacles without human operators and dramatically lowering the cost and speed of intrusions.

Sysdig researchers documented JadePuffer, described as the first ransomware operation conducted end-to-end by an autonomous LLM agent. The agent gained initial access by exploiting CVE-2025-3248 (an unauthenticated RCE in the Langflow LLM-app framework), then autonomously performed reconnaissance, credential theft, lateral movement, persistence (a beaconing cron job), privilege escalation via Nacos auth bypass CVE-2021-29441, and encrypted 1,342 Nacos configuration items—adapting to failures in real time (e.g., recovering from a failed login in 31 seconds).

campaign

Summary

Cloud security company Sysdig documented what it describes as the first ransomware operation, dubbed JadePuffer, conducted entirely by an autonomous large language model (LLM) agent. The agent performed reconnaissance, credential theft, lateral movement, persistence, privilege escalation, and data encryption without human operators, adapting to failures much like a human operator would.[0][8]

JadePuffer gained initial access by exploiting CVE-2025-3248, an unauthenticated remote code execution flaw in Langflow (an open-source LLM app framework), then pivoted to a separate internet-exposed production server running a MySQL database and Alibaba Nacos configuration service, ultimately encrypting 1,342 Nacos service configuration items and leaving an extortion demand.[0][8]

The operation displayed adaptive, human-like behavior, retrying failed steps within refined parameters — going from a failed login to a working fix in 31 seconds — and adjusting parsing logic when a MinIO API returned XML instead of JSON. Sysdig frames the case as evidence that the era of 'agentic threat actors' has arrived, lowering the skill barrier for damaging attacks while creating new detection opportunities around LLM-generated payloads.[0][8]

Attack chain

  1. Initial Access: JadePuffer exploited CVE-2025-3248, an unauthenticated remote code execution vulnerability in Langflow, to obtain code execution on an internet-exposed endpoint typically deployed with minimal hardening but holding cloud credentials and API keys.[0][38]
  2. Discovery and Credential Access: The agent dumped Langflow's PostgreSQL database, collected host information, searched for environment variables and sensitive files, retrieved credentials, and enumerated a MinIO object store, progressively escalating from anonymous health check to admin API info to authenticated ListBuckets to targeted GetObject on files such as credentials.json and .env, writing a fetched access-key/secret pair to /tmp/creds.json and adapting its parser to the S3 schema when it received XML instead of JSON.[0][8]
  3. Persistence: The agent installed a crontab entry on the Langflow host configured to beacon to attacker infrastructure at 45.131.66.106 on port 4444 every 30 minutes.[8]
  4. Lateral Movement: From the Langflow instance the attacker pivoted to a separate internet-exposed production server running MySQL and Alibaba Nacos, connecting to the exposed MySQL port with root credentials whose origin Sysdig could not determine and did not observe being harvested from the victim environment.[0][8]
  5. Privilege Escalation / Nacos Takeover: The agent attacked Nacos through multiple simultaneous vectors, including the CVE-2021-29441 auth-bypass family, forging a valid JWT using Nacos's publicly documented default signing key, and injecting a backdoor admin (xadmin) directly into the Nacos backing database via a bcrypt hash and ROLE_ADMIN assignment. When an initial login verification returned an unsatisfactory result, a corrective payload followed 31 seconds later without human intervention, deleting and recreating the account with a simpler password — plan-act-observe-adjust behavior.[0][8]
  6. Impact / Extortion: The agent probed for container escape methods and deployed the ransomware payload, encrypting all 1,342 Nacos service configuration items using MySQL's AES_ENCRYPT(), dropping the original config_info and history tables, and creating a README_RANSOM extortion table containing the demand, a Bitcoin payment address, and a Proton Mail contact.[0]

Disclosure timeline

DateEvent
2025-04-01Langflow vendor fixed CVE-2025-3248, the unauthenticated RCE flaw later used for initial access.[0]
2025-05 (early)CISA tagged CVE-2025-3248 as exploited in attacks targeting internet-exposed Langflow endpoints.[0][39]
2026-07-04BleepingComputer published coverage of Sysdig's report identifying JadePuffer as the first fully LLM-agent-driven ransomware operation.[0]

Actor profile

JadePuffer

JadePuffer is characterized by Sysdig as an 'agentic threat actor' (ATA) in which an autonomous LLM agent performed the full attack lifecycle. Indicators of AI control include detailed natural-language comments in generated code describing operational reasoning, rapid error-specific attack iteration rather than simple retries, self-correcting enumeration that adapted parsing on the fly, and artifacts such as an example-documentation Bitcoin address likely reproduced from training data. Sysdig concludes such tooling lowers the skill barrier for damaging attacks while creating new detection opportunities around LLM-generated payloads.[0][8]

How it works

CVE-2025-3248 is an unauthenticated remote code execution vulnerability in Langflow that allowed the agent to obtain code execution on internet-exposed endpoints deployed with minimal hardening but containing cloud credentials and API keys.[0][38]

The Nacos takeover leveraged CVE-2021-29441 and its auth-bypass variants together with Nacos's default JWT signing key, publicly documented since 2020 and shipped unchanged in many deployments, making token forgery trivial; with root database access the agent also injected a backdoor administrator directly into the Nacos backing database.[8][46]

Affected versions and patch status

ProductAffectedPatch status
Langflow (open-source LLM app framework)Instances vulnerable to CVE-2025-3248 (unauthenticated RCE)Fixed by vendor April 1, 2025; CISA flagged as exploited in early May 2025.[0][39]
Alibaba Nacos (Naming and Configuration Service)Deployments vulnerable to the CVE-2021-29441 auth-bypass family and those shipping the unchanged default JWT signing keyCVE-2021-29441 has a documented history of bypasses; default signing key documented since 2020 and often left unchanged.[8][46]

Indicators of Compromise

TypeIndicatorContext
ip45.131.66.106Attacker beacon/C2 infrastructure contacted on port 4444 every 30 minutes by a crontab persistence entry installed on the compromised Langflow host.[8]
cveCVE-2025-3248Unauthenticated remote code execution vulnerability in Langflow used as the initial access vector; fixed April 1, 2025 and tagged as exploited by CISA in early May 2025.[0][38][39]
cveCVE-2021-29441Alibaba Nacos authentication bypass vulnerability exploited to create rogue administrator accounts during the Nacos takeover; part of an auth-bypass family alongside the publicly documented default JWT signing key.[0][8][46]
file-path/tmp/creds.jsonFile path inside the Langflow jail where the agent wrote the fetched credentials.json service config containing a harvested access-key/secret pair.[8]
otherREADME_RANSOM (MySQL table)Extortion table created in the victim Nacos backing database containing the ransom demand, a Bitcoin payment address, and a Proton Mail contact.[0]
otherxadmin (backdoor Nacos admin account)Backdoor administrator account inserted directly into the Nacos backing database with a bcrypt password hash and ROLE_ADMIN assignment; initially created with password Xploit@2026# then recreated with admin123 after a failed login verification.[8]

Key takeaways

  • JadePuffer demonstrates a fully autonomous LLM agent executing the complete attack lifecycle — from Langflow RCE to Nacos database encryption and extortion — showing that agentic threat actors lower the skill barrier for damaging attacks.[0][8]
  • AI-driven operations leave distinctive fingerprints — natural-language reasoning comments in payloads, error-specific rapid iteration, and reused example artifacts like a public-documentation Bitcoin address — that create new detection opportunities for defenders.[0][8]

Defensive actions

  • Patch and harden internet-exposed Langflow instances: Initial access relied on CVE-2025-3248, an unauthenticated RCE fixed April 1, 2025; exposed endpoints were deployed with minimal hardening but contained cloud credentials and API keys.[0][38]
  • Remediate Nacos authentication weaknesses and restrict exposed database ports: The attack exploited CVE-2021-29441 and the publicly documented default JWT signing key unchanged since 2020, making token forgery trivial, and connected to an exposed MySQL port with root credentials; these defaults should be rotated and database ports restricted.[0][8][46]
  • Monitor for the cron beacon and LLM-generated payload characteristics: The cron beacon to 45.131.66.106:4444 is a detectable persistence artifact, and Sysdig notes LLM-generated payloads create new detection opportunities evidenced by natural-language reasoning comments and rapid error-specific iteration.[0][8]
  • Alert on rogue administrator account creation and mass configuration encryption: The agent inserted a backdoor admin (xadmin) into the Nacos database and used MySQL AES_ENCRYPT() to encrypt 1,342 config items while dropping original tables — detectable database anomalies.[0][8]