A workforce password flipped through Microsoft’s own reset screens, the existing SMS or voice challenge cleared within minutes, and an attacker-owned Microsoft Authenticator method was already on the account. According to Microsoft Threat Intelligence, Storm-3350 reset Entra account passwords through the legitimate self-service password-reset flow, signed in almost immediately, completed each account’s SMS or voice multifactor authentication challenge, and registered its own Authenticator method for lasting access. Microsoft began observing the Brazil-focused cluster in October 2026, disclosed it on 10 November 2026, and described post-takeover reconnaissance plus extensive collection from Microsoft Graph, Microsoft 365, and Azure. Named victim organizations and affected record counts were not published.

How Storm-3350 finished SSPR with SMS and voice codes

Storm-3350’s confirmed path did not need a custom password-reset portal. The actor used Microsoft’s legitimate self-service password-reset flow against workforce Entra identities, then signed in within minutes of the reset. That timing matters. The password was already attacker-controlled before the multifactor step even ran.

Microsoft states the actor completed the account’s existing SMS or voice MFA challenge on those sign-ins. SMS and voice codes are transferable factors. Anyone who can hear, read, or relay the code can satisfy the prompt. Microsoft suggests an ability to intercept or receive codes sent to the registered phone number, potentially through social engineering involving employees’ personal phones. The exact intercept path for every intrusion is not confirmed in the disclosure. Voice phishing and identity-focused impersonation are the opening patterns Microsoft ties to the cluster.

That combination is a classic workforce identity failure. The reset is real. The MFA method is real. The code still leaves the user’s device as something a coach, a second handset, or a social-engineered call can capture. Financial-services, payments, banking, and digital-asset organizations sat in the primary focus Microsoft described, with observed activity also touching healthcare, transportation, and logistics. None of that industry mix changes the mechanism. A spoken or texted second factor still travels off the enrolled phone.

Control What happened here Why it failed
Entra password via SSPR Actor reset through Microsoft’s real flow Password became attacker-held
SMS or voice MFA Challenge completed minutes after reset Code is transferable under coaching
Personal phone channel Codes tied to registered numbers Social engineering can reach the handset

Defenders hunting this pattern should treat a password reset followed by an immediate successful MFA completion as one sequence, not two unrelated events. Microsoft’s own investigation order starts there: password reset, immediate sign-in using existing MFA, then authentication-method registration.

Attacker Authenticator methods after the first sign-in

Persistence came next, still on the identity plane. After the first successful sign-in, Storm-3350 registered an attacker-controlled Microsoft Authenticator method on the compromised Entra account. According to Microsoft Threat Intelligence, that new method provides ongoing access that no longer required the victim or the victim’s phone.

The first SMS or voice win only had to work once. From that point the actor owned a first-party authenticator registration the tenant treated as legitimate. Later sign-ins no longer needed the employee’s handset, a fresh vishing call, or another code intercept. Method registration after takeover is how short-lived social engineering becomes durable account control.

Unproofed authentication-method changes are the gap. If a session that began with a transferable factor can add a new authenticator without an already-enrolled strong device approving the change, the attacker writes themselves into the account’s recovery story. Password rotation alone does not eject that method. Session cleanup that ignores authentication methods leaves a door the actor already installed.

Microsoft also warned that related clusters share tactics, infrastructure patterns, and operational dependencies, so individual IP addresses, domains, or lure themes alone are insufficient for definitive actor attribution. Focusing on one IOC while ignoring reset-plus-method-registration chains misses the durable foothold.

Graph searches, key files, and Azure collection after takeover

Once the account was theirs, Storm-3350 moved into cloud collection. Microsoft describes anomalous token acquisition and extensive activity across Microsoft Graph, Microsoft 365, and Azure. That work included SharePoint searches for "AKIA", access to .key, .pem, and .ppk material, and requests for Azure storage-account keys and application publishing profiles. Mailbox, OneDrive, and SharePoint discovery sat in the same defender sequence Microsoft published for investigations.

Those steps sit after authentication. Live sessions and API tokens already existed. No login prompt stood between the actor and Graph queries or storage-key requests. MFA at the original sign-in does not unwind tokens already issued to a session the attacker controls. Containment at this stage is revoke, rotate keys and secrets found in the hunt, strip attacker-registered authentication methods, and walk the full sequence Microsoft lists rather than stopping at the password event.

The blast radius is identity-shaped even without a separate federation story in the disclosure. One Entra workforce account with Graph and Azure reach becomes a search engine for cloud credentials and publishing profiles. AKIA-style strings and private key file extensions are exactly the kind of secondary material that turns a single mailbox-capable identity into wider cloud access. Microsoft did not publish ransom figures or extortion notes for this cluster. The operational signal is reconnaissance and bulk retrieval, not a public leak site write-up.

Helpdesk-style recovery abuse and coached code transfer are the same industrial class here: a human is steered into handing over a transferable factor so the attacker can finish a real Microsoft flow. Closing that class means removing codes anyone can read aloud or relay. A fix that drops phishable SMS, voice, and unproofed method enrollment exists; the attack write-up stops at what failed.

The defensive side of this case is covered in the related article on mfa2point0.com: preventing Storm-3350 SSPR and SMS Entra takeover.

FAQ

How did Storm-3350 take over Microsoft Entra accounts?

Storm-3350 took over Microsoft Entra accounts by resetting workforce passwords through Microsoft’s legitimate self-service password-reset flow, signing in within minutes, completing each account’s existing SMS or voice MFA challenge, and then registering an attacker-controlled Microsoft Authenticator method. According to Microsoft Threat Intelligence, the new Authenticator method gave ongoing access that no longer required the victim or the victim’s phone.

Did Storm-3350 bypass MFA on these Entra accounts?

Storm-3350 did not skip multifactor authentication on the confirmed path. The actor completed the account’s existing SMS or voice MFA challenge after the SSPR password reset. SMS and voice codes are transferable, and Microsoft suggests the actor could intercept or receive codes sent to registered phone numbers, potentially by socially engineering employees’ personal phones.

What did Storm-3350 do after the first successful sign-in?

After the first successful sign-in, Storm-3350 registered its own Microsoft Authenticator method, then ran reconnaissance and extensive collection from Microsoft Graph, Microsoft 365, and Azure. Microsoft describes SharePoint searches for AKIA strings, access to .key/.pem/.ppk files, and requests for Azure storage-account keys and application publishing profiles as part of that post-takeover activity.

Which organizations did Storm-3350 hit?

Microsoft has not named individual victim organizations for Storm-3350. The disclosure describes a Brazil-focused cluster observed from October 2026 with primary focus on financial-services, payments, banking, and digital-asset organizations, plus Microsoft-observed activity in healthcare, transportation, and logistics. Affected record counts were not published.

What should defenders hunt first after a suspected Storm-3350 intrusion?

Defenders should hunt the sequence Microsoft published: password reset, immediate sign-in that completes existing MFA, authentication-method registration, anomalous token acquisition, Graph and Azure control-plane reconnaissance, SharePoint/OneDrive/mailbox discovery, sensitive-content searches, credential and key requests, then high-volume retrieval. Strip attacker-registered methods, revoke sessions, and rotate any secrets the collection stage may have touched.