Skip to main content
Back
IntrusionMicrosoft Entra · Azure · On-premises · SaaS
23 min read

Storm-0501 cloud-based ransomware in Azure

Victim
A large enterprise with multiple subsidiaries (unnamed)
When
not statedDisclosed Aug 27, 2025
Entry
Domain administrator rights in a subsidiary's on-premises Active Directory domain, then the Directory Synchronization Accounts of two Entra Connect servers and a synced non-human identity that held Global Administrator with no registered MFA method; how the actor first entered the enterprise is not described in any source.

Microsoft Threat Intelligence reported on August 27, 2025 that Storm-0501 compromised a large enterprise made of multiple subsidiaries, starting from domain administrator rights in one subsidiary's Active Directory domain. Through the sync accounts of two Entra Connect servers the actor took over a synced Global Administrator identity that had no MFA method, gained User Access Administrator and Owner over the second tenant's Azure subscriptions, copied data out, deleted data and backups, encrypted what it could not delete, and demanded ransom over Microsoft Teams. The post gives no date for any step, no counts and no outcome.

What happened

Internet
Microsoft Entra IDsync accounts, sign-ins
Azure Subscriptions
Second Entra Tenant
+ domain controllers
+ Entra Connect servers
+ hybrid-joined server
Subsidiary AD Domains
+ sync account
+ privileged users
+ Azure resources
First Entra Tenant
Root Scope
Locks and Immutability
Storage Accounts
Snapshots and Backups
Sync Account
Global Administrator
Federation Settings
Microsoft Teams

Replaying the Storm-0501 intrusion reported in August 2025

  1. 1

    On-premises foothold

    Not stated · before Aug 27, 2025

    The actor already holds domain administrator rights in a subsidiary's Active Directory domain and reaches an Entra Connect Sync server that Defender for Endpoint does not cover; how it got in is not described.

  2. 2

    Sync accounts into the tenants

    Not stated · before Aug 27, 2025

    The first tenant's sync account enumerates users, roles and Azure resources, and sign-ins as its privileged users are refused by Conditional Access and MFA; the actor takes the sync account of a second Entra Connect server, tied to a second tenant, and repeats the reconnaissance there.

  3. 3

    Global Administrator and a federated backdoor

    Not stated · before Aug 27, 2025

    In the second tenant a synced Global Administrator identity with no MFA method gets a new password through sync and an MFA method the actor registers; a hybrid-joined server meets the Azure portal's device condition, and an actor-owned tenant becomes a trusted federated domain.

  4. 4

    Azure control plane

    Not stated · before Aug 27, 2025

    The Global Administrator calls elevateAccess for the User Access Administrator role over all the organization, assigns itself Owner over all the Azure subscriptions available, and maps the Azure Policies, resource locks and immutability policies.

  5. 5

    Exfiltration, destruction and extortion

    Not stated · before Aug 27, 2025

    The actor opens storage accounts to the internet, takes their keys and copies the data out; it deletes snapshots, restore points, storage accounts and backup containers, removing the locks and immutability policies it can; it encrypts what it cannot delete with a key it then deletes, and demands ransom over Microsoft Teams.

Impact

Data copied out of storage accounts to the actor's infrastructure; snapshots, restore point collections, storage accounts and backup protection containers deleted; the blobs the actor could not delete encrypted with a key it then deleted; a ransom demanded over Microsoft Teams. The sources give no counts, no data volume, no ransom amount and no outcome.

Outcome

Where cloud-provider controls fit

Conditional Access and MFA already refused the sign-ins as the first tenant's privileged users. In your tenants, a Conditional Access gate on MFA registration would have refused the registration that made the reset password usable, Global Administrator held only as an eligible assignment in Privileged Identity Management would have put the role behind an approved activation, and a federated token validation policy would have kept the backdoor's tokens to the actor's own domain. In your Azure subscriptions, Azure Policy denies on role assignments and on public storage access would have refused the Owner grant and the exposure unless the actor removed them first; locked immutability policies would have refused the deletion of the data they hold, a Resource Guard in another tenant would have held back the deletion of backup protection with its data, and Key Vault purge protection would have kept the deleted key recoverable for the retention period. The on-premises domains, the sync servers and the Teams message stay with their own layers.

Could this have been prevented?

In hindsight, not as a whole. 2 controls would have refused a step outright, and 18 controls would have limited one. 5 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.

2
Prevented
18
Contained
5
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

Internet
Microsoft Entra IDsync accounts, sign-ins
Azure Subscriptions
Second Entra Tenant
+ domain controllers
+ Entra Connect servers
+ hybrid-joined server
Subsidiary AD Domains
+ sync account
+ privileged users
+ Azure resources
First Entra Tenant
Root Scope
Locks and Immutability
Storage Accounts
Snapshots and Backups
Sync Account
Global Administrator
Federation Settings
Microsoft Teams

Replaying the Storm-0501 intrusion reported in August 2025

1 · On-premises foothold

3 Not covered

2 · Sync accounts into the tenants

5 Contained1 Not covered6 on other clouds

3 · Global Administrator and a federated backdoor

1 Prevented4 Contained9 on other clouds

4 · Azure control plane

2 Contained3 on other clouds

5 · Exfiltration, destruction and extortion

1 Prevented7 Contained1 Not covered13 on other clouds

Key facts

  • Sign-in attempts as several privileged users of the first tenant were blocked by Conditional Access policies and MFA requirements
  • In the second tenant a synced non-human identity held the Global Administrator role with no registered MFA method; the actor reset its on-premises password, which Password Hash Synchronization carried to the cloud, and registered an MFA method of its own
  • The actor registered its own Entra ID tenant as a trusted federated domain of the victim tenant, which let it craft SAML tokens to sign in as almost any user
  • With elevateAccess the actor gained the User Access Administrator role over all the organization, and it assigned itself Owner over all the Azure subscriptions available
  • Azure resource locks and immutability policies blocked some deletions; the actor deleted multiple locks and immutability policies, and for the immutable resources it could not delete it encrypted the blobs with a new customer-managed key and deleted the key; Key Vault soft delete keeps a deleted key for 90 days by default
  • Microsoft published its account on August 27, 2025 with no date for any step and no count, ransom amount or outcome; the victim is unnamed

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    Storm-0501's evolving techniques lead to cloud-based ransomwareMicrosoft Threat Intelligence · Aug 27, 2025 · ResearchAttack chain, victim structure, Entra identities and roles, Azure operations, exfiltration, deletion, encryption, extortion, mitigations and detections
  2. 2.
    Storm-0501: Ransomware attacks expanding to hybrid cloud environmentsMicrosoft Threat Intelligence · Aug 27, 2025 · ResearchActor history and the 2024 campaign as context, and the update note on the shift to cloud-based ransomware
  3. 3.
    The intruder is in the house: Storm-0501 attacked Azure, stole data, demanded payment via TeamsThe Register · Aug 27, 2025 · NewsDisclosure timeline, the timing of Entra Connect application-based authentication, and the absence of a victim name and a ransom amount
  4. 4.
    Microsoft details Storm-0501's focus on ransomware in the cloudCyberScoop · Aug 27, 2025 · NewsMicrosoft's statement to the press and the subsidiaries' separate tenants and uneven tooling
  5. 5.
    Ransomware Actor Deletes Data and Backups Post-Exfiltration on AzureInfosecurity Magazine · Aug 28, 2025 · NewsMicrosoft's second statement to the press, the two tenants affected and the blocked privileged sign-ins

The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.

More cloud attack breakdowns

All breakdowns