Security

Storm-3168 Azure Attacks Target Service Principals

3 min read

Summary

Microsoft Security Research detailed Azure-focused attacks by Storm-3168, a threat actor linked to agentic ransomware activity that used compromised service principals for reconnaissance, destructive actions, and credential collection. The findings highlight the growing risk of exposed workload identity secrets and reinforce the need for least privilege, secret rotation, recovery protection, and Defender for Cloud protections.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published new research on Storm-3168, a threat actor linked to JADEPUFFER, showing how compromised service principals can be used to rapidly damage Azure environments. For IT and security teams, this is an important reminder that workload identities are now a high-value target and can enable large-scale destructive operations when overprivileged or exposed.

What Microsoft found

According to Microsoft Security Research, Storm-3168 used two compromised service principals in the same tenant to carry out Azure reconnaissance, resource destruction, and credential collection.

Key findings

  • One service principal performed broad discovery of subscriptions, resource groups, virtual machines, and other resources.
  • A second service principal carried out destructive activity and later collected storage account keys.
  • The destructive sequence began shortly after reconnaissance and included more than 100 storage account deletion attempts.
  • Attackers also deleted an Azure Key Vault, Function App, and App Service plan.
  • Attempts to delete Azure SQL databases failed because the actor used an unsupported API version.
  • The actor also targeted recovery-related protections, including Azure Site Recovery and backup locks.

Microsoft said the activity strongly suggests automated or scripted execution, with overlapping token use and tightly timed operations. This aligns with a broader trend toward AI-orchestrated or agentic cloud attacks.

Why this matters for administrators

The most important lesson is that exposed credentials remain dangerous until they are revoked or rotated. In this case, Microsoft noted that a client ID, client secret, and tenant ID had previously been exposed in a public GitHub issue. Even if the secret is later removed from view, public edit history can still preserve it.

This incident also shows how existing Azure role assignments can be abused if a service principal is compromised. If the identity has contributor-level access, an attacker may be able to delete business-critical resources, collect storage keys, and interfere with recovery operations.

Admins should review Microsoft’s mitigation guidance and prioritize these actions:

  • Audit service principals and other workload identities for excessive permissions.
  • Rotate or revoke any secrets that may have been exposed publicly.
  • Enforce least privilege for app registrations and service principals.
  • Protect backup, recovery, and lock configurations with independent safeguards.
  • Enable Microsoft Defender for Cloud protections and alerts for suspicious identity and resource activity.
  • Monitor for unusual ARM operations such as bulk enumeration, ListKeys requests, and rapid deletion attempts.

Bottom line

Storm-3168 demonstrates how quickly attackers can move from cloud discovery to destructive impact when service principals are compromised. Organizations using Azure should treat workload identity security, secret hygiene, and recovery protection as core parts of their cloud defense strategy.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Azureservice principalsworkload identitiesMicrosoft Defender for Cloudcloud security

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.