What happened
Replaying the Storm-0558 May 2023 intrusion
- 1
An old consumer key stays trusted
2016 to 2023: key created in 2016, due to retire in March 2021; one key list from September 2018, mail systems on it from 2022Microsoft's 2016 consumer key outlives its planned retirement, and one key list with no scope check lets the mail systems trust it for enterprise tokens.
- 2
The key leaves Microsoft by an unknown path
2021 for the engineer's account (April to August, late 2021 or after April, by source); when the key left is unknownThe actor signs in to Microsoft's corporate network as an engineer, and the 2016 key reaches the actor by a path no source confirms.
- 3
Forged tokens open enterprise mail
From May 15, 2023 (Microsoft) until the key stopped working in OWA: June 24 (CSRB) or June 27, 2023 (Microsoft)Tokens forged with the key pass Microsoft's validation, OWA accepts them as enterprise users' tokens, and its token API renews them.
- 4
Mailboxes read and downloaded
May and June 2023 (CSRB): at State June 13 to 24, at Commerce from June 6 by later logs; Microsoft blocked the key for consumer customers on July 3Scripts download mail from the victim organizations' mailboxes, and forged consumer tokens open related personal accounts on Outlook.com.
- 5
Found by a customer, then the key is invalidated
Alerts on 15 or June 16, 2023 (CSRB), mid-June (CISA); key invalidated June 24 (CSRB) or blocked in OWA June 27 (Microsoft)State's SOC flags mailbox reads by an unexpected application and tells Microsoft, which finds the forgery and invalidates the key.
From May 15, 2023 by Microsoft's date, possibly earlier by what the CSRB heard, until the key stopped working in late June 2023, the actor read and downloaded email from the Exchange Online mailboxes of about 25 organizations by Microsoft's July 11, 2023 count, or 22 enterprise organizations by Microsoft's determination as the CSRB reports it, government agencies among them, and from related personal accounts: 503 by the CSRB's report. It took about 60,000 emails from the State Department alone, per the CSRB, and an unknown number in the U.K. Microsoft says the post-compromise activity was limited to email access and exfiltration for targeted users and is confident only Exchange Online was impacted; the CSRB and Wiz say the key could have opened other applications that trusted it, and Microsoft called Wiz's analysis hypothetical.
No tenant control refuses a token the provider signs
This intrusion ran inside Microsoft's own systems. The tokens were signed with Microsoft's own consumer key, checked by Microsoft's own identity platform and accepted by Microsoft's own mail service. No control in your tenant refuses a token that the provider itself signs, and the sources name no Microsoft Entra Conditional Access, multifactor authentication or session setting that applied to these tokens. What the sources say you could do is reactive: turn on and watch the MailItemsAccessed audit record. That is how the State Department's own rule on the record flagged mailbox access that departed from an application's baseline, and State reported it to Microsoft. The record refuses nothing, and in 2023 it needed Microsoft Purview Audit (Premium) with G5/E5 licensing, which few, if any, other victims had. Microsoft's 2026 documentation lists it in Audit (Standard), on by default for E3/E5 users. The fix was Microsoft's: it invalidated the key, closed the validation flaw and says no customer action is required.
Could this have been prevented?
In hindsight, no: no cloud-provider control reaches these steps. 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.
- 0
- Prevented
- 0
- Contained
- 11
- 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.
Replaying the Storm-0558 May 2023 intrusion
1 · An old consumer key stays trusted
2 Not covered2 · The key leaves Microsoft by an unknown path
2 Not covered3 · Forged tokens open enterprise mail
3 Not covered4 · Mailboxes read and downloaded
2 Not covered5 · Found by a customer, then the key is invalidated
2 Not coveredKey facts
- Microsoft created the consumer signing key in 2016 and planned to retire it in March 2021; it stopped manual rotation in 2021, and the key stayed in Microsoft's public key list until it was replaced between June 27 and July 5, 2023
- From May 15, 2023, by Microsoft's investigation, the actor reached email accounts at about 25 organizations; the CSRB reported Microsoft's determination of 22 enterprise organizations and 503 related personal accounts, and heard that access may have started earlier because logs were kept for 30 days
- The actor downloaded about 60,000 emails from the State Department alone, per the CSRB; a Senate staffer relayed 60,000 emails from 10 State Department accounts
- The State Department found the activity with a custom rule on the MailItemsAccessed log, which in 2023 needed Microsoft Purview Audit (Premium) and G5/E5 licensing, and reported it to Microsoft on June 16, 2023
- The CSRB dated the key's invalidation to June 24, 2023; Microsoft's own dates were June 27 for blocking tokens signed with the key in OWA, June 29 for completing the replacement and July 3 for blocking the key for all impacted consumer customers
- How and when the actor obtained the key is unknown: Microsoft has found no crash dump containing it, and the CSRB report, released on April 2, 2024, found the intrusion preventable
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.Microsoft mitigates China-based threat actor Storm-0558 targeting of customer emailMicrosoft Security Response Center (MSRC) · Sep 6, 2023 · Vendor reportstart date, customer report, organization count, forged-token mechanism, services observed, mitigation, notification, customer guidance
- 2.Analysis of Storm-0558 techniques for unauthorized email accessMicrosoft Threat Intelligence · Jul 14, 2023 · Vendor reportactor profile, mitigation dates, token forging and replay, API design flaw, tooling, infrastructure, key hardening
- 3.Results of Major Technical Investigations for Storm-0558 Key AcquisitionMicrosoft Security Response Center (MSRC) · Mar 12, 2024 · Vendor reportkey acquisition hypothesis and correction, engineer account compromise, token validation flaw, environment controls, fixes
- 4.Enhanced Monitoring to Detect APT Activity Targeting Outlook Online (AA23-193A)CISA and FBI · Jul 14, 2023 · Advisorydetection method, MailItemsAccessed, licensing, logging guidance, Microsoft determination
- 5.Review of the Summer 2023 Microsoft Exchange Online IntrusionCyber Safety Review Board (U.S. Department of Homeland Security) · Mar 20, 2024 · Advisoryvictim counts, detection, State and Commerce timelines, key history and rotation, token validation flaw, token path, 2021 corporate compromise, remediation, notification, logging, findings, other providers' token and key practices
- 6.Cyber Safety Review Board Releases Report on Microsoft Online Exchange Incident from Summer 2023U.S. Department of Homeland Security · Jan 20, 2025 · Advisoryreport release date, summary of findings
- 7.Compromised Microsoft Key: More Impactful Than We ThoughtWiz Research · Jul 21, 2023 · Researchkey validity, key list replacement window, application types exposed, offline forging, cached keys
- 8.How Microsoft is expanding cloud logging to give customers deeper security visibilityMicrosoft Security · Jul 19, 2023 · Vendor reportaudit log availability change, retention change, timing
- 9.Securing our future: April 2025 progress report on Microsoft's Secure Future InitiativeMicrosoft Security · Apr 21, 2025 · Vendor reportpost-incident signing key protection, automatic rotation, confidential VMs
- 10.Use MailItemsAccessed to investigate compromised accountsMicrosoft Learn (Microsoft Purview documentation) · Jun 19, 2026 · Vendor reportMailItemsAccessed tier and default as documented in 2026
- 11.Chinese hackers stole 60,000 emails from US State Department in Microsoft hack, Senate staffer saysReuters (syndicated by The Star) · Sep 28, 2023 · NewsState email count and account count as briefed to senators
- 12.Microsoft downplays damaging report on Chinese hacking its own engineers vettedCyberScoop · Jul 31, 2023 · NewsMicrosoft response to Wiz analysis
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.