# Microsoft: Storm-3168 ran agentic-style Azure destruction and key theft, linked to JADEPUFFER

- ID: microsoft-storm-3168-ran-agentic-style-2026-09
- Reported: 2026-09-25
- Researcher: unknown
- Organization: Microsoft Threat Intelligence
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: not assessed
- Entry page: https://openattacks.ai/attacks/microsoft-storm-3168-ran-agentic-style-2026-09/
- Entry JSON: https://openattacks.ai/api/attacks/microsoft-storm-3168-ran-agentic-style-2026-09.json
- Browse title: Microsoft: Storm-3168 ran agentic-style Azure destruction and key theft, linked to JADEPUFFER
- Editorial summary: Microsoft tied a two-identity Azure attack, with 15 hours of recon then a seven-minute destructive burst, to the agentic ransomware actor JADEPUFFER.
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/microsoft-storm-3168-ran-agentic-style-2026-09.json

## Technique
Microsoft tied a two-identity Azure attack, with 15 hours of recon then a seven-minute destructive burst, to the agentic ransomware actor JADEPUFFER.

## Stack relevance (editorial)
Assessment: not\_assessed. No reviewed applicability annotation is available. Product mentions do not establish victim conditions.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
unknown

## AI tooling and models
- None named
- activity assessed as AI-orchestrated

## Other tooling
- unknown

## Victims and sectors
Multiple sectors

## Target geography
- unknown
Target geography was not captured by the Notion feed. Actor attribution is not used as a victim location.

## Attribution
Storm-3168 (linked to JADEPUFFER)

## Scale and metrics
unknown

## Attack flow
Summary diagram derived from entry fields; a detailed sequence has not been supplied.
### entry: Reported initial access [unknown]
unknown
Evidence: https://www.microsoft.com/en-us/security/blog/2026/09/25/storm-3168-agentic-driven-cloud-attacks-using-compromised-service-principals/ ; https://labs.cloudsecurityalliance.org/research/csa-research-note-storm3168-jadepuffer-azure-agentic-attack/

### activity: Reported activity [execution]
Microsoft tied a two-identity Azure attack, with 15 hours of recon then a seven-minute destructive burst, to the agentic ransomware actor JADEPUFFER.
Evidence: https://www.microsoft.com/en-us/security/blog/2026/09/25/storm-3168-agentic-driven-cloud-attacks-using-compromised-service-principals/ ; https://labs.cloudsecurityalliance.org/research/csa-research-note-storm3168-jadepuffer-azure-agentic-attack/

### ai: AI involvement [ai]
None named · activity assessed as AI-orchestrated
Evidence: https://www.microsoft.com/en-us/security/blog/2026/09/25/storm-3168-agentic-driven-cloud-attacks-using-compromised-service-principals/ ; https://labs.cloudsecurityalliance.org/research/csa-research-note-storm3168-jadepuffer-azure-agentic-attack/

Connections:
- entry -> activity
- ai -> activity (AI context)

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### entry: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### activity: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### ai: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
No source-backed mapping is currently recorded.

## Defensive notes
unknown

## Sources
- https://www.microsoft.com/en-us/security/blog/2026/09/25/storm-3168-agentic-driven-cloud-attacks-using-compromised-service-principals/
- https://labs.cloudsecurityalliance.org/research/csa-research-note-storm3168-jadepuffer-azure-agentic-attack/

## Source notes
Imported from the AI Threat Watch Notion feed (an automated daily scan); not yet editorially reviewed. Feed severity: Medium. Feed novelty: Evolution.
