JadePuffer Hackers Exploit Azure Identities for Destructive Cloud Attacks
Microsoft reveals how Storm-3168 used stolen service principals to delete critical Azure resources.
1First Agentic Ransomware
JadePuffer made history as the first documented agentic ransomware where an LLM autonomously executed the entire attack chain. The operation progressed from initial access to database server compromise and data destruction without human intervention. Microsoft's July discovery revealed this novel threat that blurred lines between automated and AI-driven attacks. The same group, tracked as Storm-3168, later pivoted to Azure identity attacks.
2Azure Identity Hijacking
Storm-3168 compromised two service principals belonging to the same cloud tenant during an 18-hour attack window in June. Researchers found the attackers likely gained initial access through exposed credentials in a public GitHub issue. The compromised identities showed identical network fingerprints and used python-requests/2.34.2 user agent, suggesting coordinated automation rather than manual intrusion.
3Reconnaissance Phase
The first service principal conducted 15.5 hours of extensive reconnaissance, executing over 300 successful read operations. It mapped the victim's Azure environment including Virtual Machines, subscriptions, and resource groups. This intelligence gathering provided attackers complete visibility of the cloud infrastructure before launching destructive operations. Such thorough reconnaissance is characteristic of advanced persistent threats.
4Destructive Operations
Within 35 minutes, the second service principal attempted over 150 destructive actions, successfully deleting 100+ Azure Storage accounts. The attacker also erased a Key Vault, Function App, and App Service plan supporting critical infrastructure. Most deletions succeeded except where Azure resource locks intervened. Parallel attempts to delete SQL databases failed due to unsupported API versions.
5Credential Harvesting
During the attack's final phase, the compromised identity made 30+ successful ListKeys requests for storage account access keys, including Azure Site Recovery accounts. This credential collection aligned with ransomware playbooks, though no ransom demand followed. Attackers also unsuccessfully targeted backup protection locks, indicating intent to hinder recovery efforts.
6Ransomware Indicators
Microsoft analysts noted the attack pattern—resource destruction combined with recovery mechanism interference—matched ransomware preparation tactics. The simultaneous credential harvesting suggested plans for future data exfiltration. However, the absence of a ransom note makes this either an abandoned operation or a new attack vector testing phase.
7Cloud Security Implications
The incident highlights critical vulnerabilities in Azure service principal management and credential hygiene. Attackers exploited exposed credentials rather than sophisticated zero-days. The 18-hour attack window demonstrates how prolonged access enables extensive damage. Organizations must implement stricter controls around machine identities and monitor for abnormal service principal activities.
8Emerging Threat Landscape
Storm-3168's evolution from LLM-driven ransomware to cloud identity attacks represents a dangerous escalation. The group demonstrates adaptability in combining emerging technologies with cloud platform weaknesses. This case sets precedent for automated, large-scale cloud resource destruction without human operators—a new frontier in cyber warfare requiring updated defense paradigms.