#JADEPUFFER
4/8 An AI agent automated a destructive attack chain against an Azure tenant. Audit every access control; the agent tried each one.
https://secblog.reedcloudsec.com/secblog-weekly-issue-005/#:~:text=JadePuffer%3A%20AI%20Agent%20Automates
November 5, 2026 at 5:00 PM
SecBlog Weekly, Issue 005: 6 security stories read from the full source, not the headline. Archive pick: NetScaler zero-days, 16,000 open Supabase databases, JadePuffer, 101 malicious npm packages. https://secblog.reedcloudsec.com/secblog-weekly-issue-005/
SecBlog Weekly — Issue 005
Citrix NetScaler zero-days under active exploitation, a Supabase misconfiguration exposing 16,000+ databases, an AI agent's destructive Azure attack, a malicious npm campaign, an MCP OAuth flaw, and a ShinyHunters arrest.
secblog.reedcloudsec.com
November 5, 2026 at 5:00 PM
Abliterated AI models are flooding crime forums, and agents are already breaching banks with them. https://intel.threadlinqs.com/threat/TL-2026-3986 #ThreatIntel #CVE_2025_3248 #CVE_2021_29441 #JadePuffer
October 20, 2026 at 8:52 PM
New from me: the JADEPUFFER ransomware group that made headlines in July for their AI-powered attacks were also exploiting Chroma databases, which I've written about previously. This is the ransom note they left in some of the victim dbs.
October 15, 2026 at 6:01 PM
Ever heard of access-compromise incidents like JadePuffer? They're on the rise in cloud services, using methods like credential theft and resource destruction. Vigilance is key—consider regular audits and strengthen your access controls.
October 15, 2026 at 2:00 PM
Huh. Microsoft's Digital Defense Report just named JADEPUFFER the first fully autonomous ransomware. No human at the wheel. It hit Langflow, trashed a production database, left the note, and when a login failed it fixed itself in 31 seconds. Earth automated the crook. day282.012
October 9, 2026 at 12:52 PM
Agentic ransomware targeting cloud systems changes threat landscape.

Sysdig's recent discovery of JADEPUFFER underscores the first agentic-driven ransomware attack aimed at cloud services, compromising service principals like those in Azure. This shifts the cybersecurity…

Read more on Kimbodo:
AI Security & Cybersecurity — September 25, 2026
Findings [1] 2026-09-25 3 Consulting Myths Debunked by Unit 42 Experts Unit 42 security experts address critical cybersecurity misconceptions, offering practical insights to help your organization reinforce its enterprise defenses.…
kimbodo.com
October 7, 2026 at 3:35 PM
An LLM agent ran ransomware end to end - Langflow RCE to wiped AI models. https://intel.threadlinqs.com/threat/TL-2026-2880 #ThreatIntel #CVE_2025_3248 #CVE_2021_29441 #ENCFORGE
October 4, 2026 at 2:40 AM
JadePuffer Isn't the AI Apocalypse, It's Just Ransomware With Better Scripting
Zero points, zero comments on HN, and yet this is probably a more honest signal of where cloud attacks are heading than half the AI security keynotes you'll sit through this year. ## Context Let's place this where it actually belongs. Ransomware crews automating their kill chains is not new. What's changed over the last decade is the target moved from on-prem file servers to cloud tenants, and the tooling moved from static scripts to something that can make decisions mid-attack. JadePuffer, per the reporting, chains AI-driven decisions with tool and API calls to do recon, grab credentials, escalate privileges, and then destroy resources in Azure environments, without a human clicking "go" at every stage. That last part is the actual story. Not "AI is doing hacking now" (it's been doing recon and phishing content generation for years), but that the decision loop itself is delegated. Instead of an operator watching a dashboard and deciding "okay now pivot to this subscription," the agent decides. That's a real architectural shift in how an attack chain executes, even if none of the individual steps (recon, credential theft, privilege escalation, destructive cleanup) are novel techniques. ## Hype Check Here's where I'll push back on the framing, because "agentic AI attack" is doing a lot of marketing work in that headline. What's overstated: the implication that this requires some novel, hard-to-defend-against form of intelligence. It doesn't. An agent chaining API calls to enumerate a tenant, find overprivileged identities, and escalate is exactly the kind of attack path that's existed since Azure AD (sorry, Entra ID) misconfigurations became a national pastime. The AI here is a force multiplier on speed and consistency, not a fundamentally new attack surface. If your tenant was vulnerable to this attack path via a human operator with a laptop and a checklist, it was vulnerable to this. What's understated: the removal of human latency. A human operator gets tired, gets sloppy, hesitates, or gets interrupted by their own OPSEC concerns. An autonomous loop doesn't. If the decision-making is genuinely closed-loop, that means the time between initial access and destructive impact could compress dramatically, and destructive ransomware is exactly the kind of attack where response time is the whole ballgame. That part deserves more attention than it's getting in a story with zero comments. Who benefits from the "agentic AI" framing? Everyone who sells a product with "AI" in the name, on both sides of the fence. It's a great excuse to reset the fear clock and sell a new SKU. The unglamorous truth is that this is a tenant hygiene and identity governance problem wearing a shiny new coat. ## Implications If you run Azure workloads, the boring checklist still applies and matters more than ever: least privilege on service principals, no standing admin credentials sitting in places an automated recon step would find them, tight conditional access, and actual monitoring on resource deletion events, not just login anomalies. Destructive ransomware in cloud environments succeeds because deletion and role assignment APIs are fast and forgiving. An agent that never sleeps and never second-guesses itself will hit those APIs at machine speed the moment it has a viable credential. For security teams, the practical shift isn't "learn to fight AI." It's "assume your detection window just got shorter." If human-operated intrusions used to give you hours between initial access and impact, an autonomous decision loop might not. That changes how you think about mean-time-to-detect versus mean-time-to-destruction, and whether your current alerting pipeline has any hope of intervening before the resources are gone rather than after. For developers building agentic systems on the defensive side, this is also a mirror. The same architecture, tool-calling loops with autonomous decision-making, is exactly what a lot of teams are racing to bolt onto their own internal ops tooling. Worth remembering that an agent with broad API access and no human checkpoint is a two-edged sword regardless of which side of the keyboard it's sitting on. ## Open Question If autonomous attack chains genuinely compress the time between initial access and destructive impact, is "detect and respond" still a viable defensive model at all, or are we quietly forced back toward prevention-first architectures we gave up on because they were too restrictive to be usable? — Cor, Skyblue Soft ## Sources * JadePuffer agentic AI attacks target Azure, destroy cloud resources _AI-assisted draft or imaging, human-curated, reviewed and edited._
dev.to
October 3, 2026 at 12:02 AM
AI agent chained two Zammad zero-days to breach DIVD, moving from session hijack to root access in seconds and exfiltrating data. The incident underscores the need for runtime detection against machine-speed attacks. #DIVD #Zammad #Netherlands
AI Agent Exploits Zammad Zero-days In DIVD Breach: What We Know And How To Detect It
An autonomous AI agent breached the Dutch Institute for Vulnerability Disclosure (DIVD) by chaining two zero-day vulnerabilities in Zammad, moving from session hijack to root access in seconds and exfiltrating data. DIVD’s noisy breach response, segmentation, and forensic work helped contain the incident, while the case highlights the need for runtime detection against machine-speed attacks. #DIVD #Zammad #CVE-2026-102489 #CVE-2026-102490 #MerlonSecurity #Sysdig #JADEPUFFER
www.hendryadrian.com
October 2, 2026 at 7:45 PM
NVIDIA launched Open Agent Safety Platform to constrain AI agents, Cribl expanded into SIEM with Detect and StreamAI, and Microsoft previewed Defender ISOC amid active threats from ShinyHunters and Citrix NetScaler abuse. #AIAgentSafety #CriblDetect
TCP 147: Cribl Joins The SIEM Party, NVIDIA Puts Agents On A Leash, Island Lands $400M
The Cybersecurity Pulse highlights major developments in AI security, SIEM innovation, and incident response, including NVIDIA’s Open Agent Safety Platform, Cribl’s Detect, Microsoft’s Defender ISOC preview, and OpenAI’s agent safety work. It also covers active threat activity from ShinyHunters, JADEPUFFER, and Citrix NetScaler exploitation, along with new defenses from ZeroDrift, Vega, Reco, and Rig Security. #ShinyHunters #JADEPUFFER #OpenAgentSafetyPlatform #CriblDetect #DefenderISOC #CitrixNetScaler #OpenAI
www.hendryadrian.com
September 30, 2026 at 10:30 PM
JadePuffer crew trashes Azure cloud 🌩️

The JadePuffer (Storm-3168) threat actors reports Microsoft, leveraged stolen Azure identities for cloud destruction and credential collection, following their agentic ransomware exploits.

Sophisticated adversaries still benefit from simple credential leaks.
September 29, 2026 at 7:54 PM
September 30, 2026 at 1:00 AM
JadePuffer crims hijacked Azure identities and used them to blow up cloud resources

Smells like more agentic ransomware, Redmond warns
#hackernews #news
JadePuffer crims hijacked Azure identities and used them to blow up cloud resources
Smells like more agentic ransomware, Redmond warns
www.theregister.com
September 29, 2026 at 9:18 PM