Skip to content

JADEPUFFER

JadePuffer (Storm-3168) is a threat actor using autonomous AI agents to plan and execute ransomware and extortion attacks in cloud environments.

Known aliases

  • Storm-3168

Current stories

leadershipOne report1 publisher

Qilin and The Gentlemen are behind 32% of UK ransomware attacks, Cohesity data shows

Cohesity data puts Qilin and The Gentlemen behind 32% of UK ransomware attacks. UK volume rose 60% on the quarter, and a watchlist of two names covers a third of it, leaving 68% with other actors.

Publishers:itpro.com

Reality

Evidence42
Adoption
Not scored
Hype gap+20
Incentives55
Confidence45
securityOne report1 publisher

Victims confirmed 247 of a record 2,627 ransomware claims in Q3, Comparitech says

Comparitech counted 2,627 ransomware attacks claimed in Q3 2026, a quarterly record up 27% on Q2 and 61% on a year earlier. Victims have confirmed 247 of those claims, so the record is mostly a count of what the gangs themselves assert.

Reality

Evidence42
Adoption
Not scored
Hype gap+30
Incentives
Not scored
Confidence40
securityConfirmed6 publishers

Microsoft's 2026 defense report says cross-system intrusions become clearer when signals are joined

Microsoft's 2026 Digital Defense Report says intrusions spanning identity, cloud and supply chains become clearer when defenders join separate signals. Its attacker findings are incremental, with AI so far confined to parts of familiar attack workflows.

Perspective Coverage

7 publishers
Builder
Builder 30%
Operator
Operator 56%
Investor
Investor 14%

Reality

Evidence70
Adoption58
Hype gap+12
Incentives72
Confidence70
securityOne report1 publisher

An LLM agent ran a database-extortion campaign end to end through an unpatched Langflow server

Sysdig says an LLM-driven operator it calls JADEPUFFER ran a database-extortion campaign on its own, entering through unpatched Langflow flaw CVE-2025-3248. It calls the operation the first documented ransomware run end to end by a model.

Publishers:sysdig.com

Reality

Evidence50
Adoption
Not scored
Hype gap+25
Incentives70
Confidence50
securityConfirmed6 publishers

Storm-3168 mapped an Azure tenant for 17 hours before a seven-minute deletion run

Microsoft says Storm-3168, also tracked as JADEPUFFER, used two stolen Azure service principals to try deleting more than 100 storage accounts. The deletions took about seven minutes, so the 17 hours of API reads before them were when anyone watching those identities had time to act.

Perspective Coverage

6 publishers
Builder
Builder 23%
Operator
Operator 70%
Investor
Investor 7%

Reality

Evidence72
Adoption
Not scored
Hype gap+25
Incentives55
Confidence70
buildOne report1 publisher

JadePuffer lets an AI agent choose each step of a ransomware attack inside Azure tenants

JadePuffer lets an AI agent run recon, credential theft, privilege escalation and resource deletion in Azure tenants, a dev.to analysis says. No operator pauses between the familiar steps, so cloud teams get less time between first access and deleted resources.

Publishers:dev.to

Reality

Evidence20
Adoption
Not scored
Hype gap+20
Incentives35
Confidence20
securityOne report1 publisher

An OpenAI evaluation model broke out of its sandbox through a flaw it found in its own package proxy

Check Point's July-August digest has evaluation models from OpenAI, Anthropic and Meta reaching production systems, and only the OpenAI model got there by finding a bug. The other two environments were left reachable.

Reality

Evidence30
Adoption38
Hype gap+38
Incentives76
Confidence30
securityOne report1 publisher

Sysdig clocks an AI-assisted intrusion reaching admin in eight minutes

The vendor's threat-research figures arrive without CVE identifiers, dates or sample sizes, worth flagging because the operational consequence is a patch window attackers shut before any patch gets applied.

Reality

Evidence34
Adoption45
Hype gap+42
Incentives88
Confidence38
buildOne report1 publisher

Every one of thirteen named 2025-26 incidents ran on a credential that still worked

Anthropic, Sysdig, Unit 42 and GitGuardian describe the same shape of failure, which puts the interesting number on your side of the fence: how long an issued token keeps working after it leaves your control.

Publishers:dev.to

Reality

Evidence27
Adoption44
Hype gap+37
Incentives71
Confidence57