Skip to content
NewA calmer, faster ZeroHour
Threat actorhighExploited in the wild

JADEPUFFER-Linked Attackers Used Compromised Service Principals to Delete Azure Resources

The Hacker News ()3 min read5 · 1 read
AI summary · grok-4.7Summaries by Vani AI

JADEPUFFER-linked Storm-3168 deleted Azure storage, databases, and recovery resources with stolen service principals.

Microsoft says JADEPUFFER, tracked as Storm-3168, spent about 18 hours in early June 2026 using two compromised Azure service principals for discovery and destruction. One identity performed more than 300 reads; the second ran over 150 destructive or credential-collection operations in 35 minutes, including more than 100 storage-account deletion attempts plus Key Vault, Function App, App Service, and SQL targets. Most storage deletions succeeded, while locks and an unsupported SQL API blocked some attempts, and no ransom note or confirmed exfiltration was seen. The client secret had been left in a public GitHub issue history; earlier JADEPUFFER activity used Langflow CVE-2025-3248 and the ENCFORGE ransomware.

Key facts
  • Two stolen service principals split discovery and destructive Azure operations.
  • More than 100 storage-account deletions were attempted in about seven minutes.
  • Resource locks and deletion protection blocked some storage removals.
  • The client secret remained in a public GitHub issue edit history.
  • No ransom note or successful data exfiltration was observed.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2025-3248
Unauthenticated RCE in Langflow /api/v1/validate/code
9.8100%KEVRansomwarePoC ×4
KEV

From the original article

3 min read at thehackernews.com

The threat actor known as JADEPUFFER has been observed orchestrating destructive actions within a Microsoft Azure environment using compromised service principals. Microsoft, which is tracking the activity under the name Storm-3168, has called it an evolution of the threat actor's tradecraft. The attack took place in early June 2026 over a period of about 18 hours.

The Hacker News

thehackernews.com

Read the full article at The Hacker News

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.