Full Report
Microsoft details JADEPUFFER-linked Azure reconnaissance, resource deletion, and credential access using compromised service principals, identifying the activity as associated with Storm-3168 and providing guidance for defenders. The post Storm-3168: Agentic-driven cloud attacks using compromised service principals appeared first on Microsoft Security Blog.
Analysis Summary
# Threat Actor: Storm-3168 (JADEPUFFER)
## Attribution & Identity
- **Name/Alias:** Storm-3168 (Microsoft's temporary designation).
- **Associated Groups:** Linked to activity previously tracked under the name **JADEPUFFER**.
- **Actor Type:** The actor demonstrates sophisticated knowledge of cloud environments, specifically Azure and Entra ID (formerly Azure AD).
## Activity Summary
Microsoft recently observed Storm-3168 conducting high-velocity, "agentic-driven" cloud attacks. The campaign is characterized by the use of compromised service principals to gain entry into Azure environments. Once inside, the actor performs rapid reconnaissance, credential access, and resource deletion. A notable evolution in this campaign is the suspected use of automated or agentic scripts to execute commands at a speed and scale that suggests the integration of AI-driven or highly automated tooling.
## Tactics, Techniques & Procedures
- **Initial Access:** Use of compromised service principal credentials (likely obtained via prior credential harvesting or misconfigurations).
- **Reconnaissance:** Extensive discovery of Azure resources, subscriptions, and tenant settings using automated scripts.
- **Credential Access:** Extraction of secrets from Key Vaults and adding new credentials to existing service principals to maintain persistence.
- **Impact/Disruption:** Deliberate deletion of critical cloud resources (VMs, storage accounts, network configurations).
- **Agentic Execution:** Use of automation that mimics human decision-making processes to navigate complex cloud hierarchies rapidly.
**MITRE ATT&CK IDs mentioned/implied:**
- **T1078.004:** Valid Accounts: Cloud Accounts
- **T1535:** Unused/Unsupported Cloud Permissions
- **T1087.004:** Account Discovery: Cloud Account
- **T1556:** Steal or Forge Authentication Tokens
- **T1485:** Data Destruction
## Targeting
- **Sectors:** The article indicates a broad interest in cloud-heavy industries, though specific sectors are not explicitly listed, the techniques target any organization utilizing Azure/Entra ID.
- **Geography:** Global (inherent to cloud service targeting).
- **Victims:** Organizations with misconfigured or exposed service principals and those utilizing Copilot/Agentic AI systems without proper guardrails.
## Tools & Infrastructure
- **Tools:** Use of Azure CLI and PowerShell modules for cloud management. Automated "agentic" scripts designed to interact with the Azure Resource Manager (ARM) API.
- **Infrastructure:**
- **C2/IPs:** The actor frequently rotates source IPs to bypass geographic or IP-based conditional access policies. (Note: Specific IPs were not listed in the provided snippet but are typically defanged in full reports, e.g., `127[.]0[.]0[.]1`).
- **Compromised Service Principals:** These act as the primary "infrastructure" for lateral movement within the victim's tenant.
## Implications
Storm-3168 represents a shift toward **agentic-driven attacks**, where the speed of execution outpaces traditional human-led SOC response times. By targeting service principals—which often lack Multi-Factor Authentication (MFA)—the actor can operate with high privileges and low visibility. The shift toward resource deletion indicates a potential shift from pure espionage to disruptive or extortion-based motivations.
## Mitigations
- **Service Principal Security:** Implement strict credential rotation policies and monitor for the addition of unauthorized credentials to service principals.
- **Least Privilege:** Apply the principle of least privilege (PoLP) to service principals, ensuring they only have access to necessary subscriptions and resources.
- **Conditional Access:** Enforce Workload Identity Federation and location-based policies for service principals where possible.
- **Monitoring:** Enable and monitor Entra ID sign-in logs (specifically `ServicePrincipalSignInEvents`) and Azure Activity logs for mass resource deletion or unexpected reconnaissance.
- **AI Guardrails:** If utilizing agentic systems (like Copilot Studio), implement the recommended prompt injection protections and AI-specific security configurations mentioned in Microsoft's documentation.