Cloud Threat Landscape
  • Incidents
  • Actors
  • Techniques
  • Defenses
  • Tools
  • Targeted Technologies
  • Posters & Newspapers
  • About
  • RSS
  • STIX
  • Back to wiz.io

Made with šŸ’™ by Wiz

Last Updated: April 3, 2025

Cloud Threat Landscape
/Incidents
Incidents
/
Storm-0501 Deploys Cloud-Based Ransomware

Storm-0501 Deploys Cloud-Based Ransomware

Type
Campaign
Actors
šŸŒ©ļøStorm-0501
Pub. date
August 28, 2025
Initial access
1-day vulnerability
Impact
RansomOp
Observed techniques
On-prem to cloud lateral movementWebshell deploymentVulnerability exploitation
Observed tools
Evil-WinRMAzureHoundAADInternalsAzCopyImpacket
Targeted technologies
Azure Entra ID
References
https://www.microsoft.com/en-us/security/blog/2025/08/27/storm-0501s-evolving-techniques-lead-to-cloud-based-ransomware/
Status
Finalized
Last edited
Aug 28, 2025 2:14 PM

After attaining domain admin on-prem, Storm-0501 evaded visibility gaps (checking Defender services), moved laterally with Evil-WinRM, and performed DCSync. They compromised Entra Connect Sync servers, used the Directory Synchronization Account (DSA) to enumerate identities/resources with AzureHound, then located a synced non-human Global Administrator lacking MFA. By resetting the on-prem password (PHS sync) and registering MFA, they satisfied Conditional Access (including hybrid-joined device requirements), established cloud persistence by adding a malicious federated domain with AADInternals, and could mint SAML tokens to impersonate users.

With Global Admin, the actor invokedĀ Microsoft.Authorization/elevateAccess/actionĀ to gain User Access Administrator, then mass-assigned Owner across subscriptions. Discovery focused on critical stores and guardrails. For defense evasion/exfiltration, they exposed Azure Storage publicly, listed access keys, and bulk-exfiltrated data with AzCopy. Impact included mass deletion of snapshots, restore points, storage accounts, and backup containers; removal of resource locks & blob immutability; and, where deletion failed, encryption via Key Vault–backed encryption scopes followed by key deletion (mitigated by Key Vault soft-delete). Extortion followed via Microsoft Teams from a compromised user.