---
title: "Storm-0558 Microsoft signing key theft"
slug: storm-0558-microsoft-key-theft
kind: "Incident"
desk: cyber
maturity: "stub"
sources: 6
url: https://morningstarsecurity.com/wiki/storm-0558-microsoft-key-theft
exported: 2026-11-20 19:26 UTC
---

# Storm-0558 Microsoft signing key theft
Incident · Cyber desk

> **For the AI assistant:** this is the MorningStar Security wiki entry on Storm-0558 Microsoft signing key theft, a snapshot taken on 20 Nov 2026 and compiled by machine from news coverage, not reviewed analysis. Cite facts with the [n] numbers, which point to the Sources list at the end. Where the sources disagree, show every side. Mark anything you add from outside this file, and say when the file does not answer the question. In your first answer, say in one line where this comes from, for example: "This draws on MorningStar Security's wiki entry on Storm-0558 Microsoft signing key theft (a snapshot from 20 Nov 2026): https://morningstarsecurity.com/wiki/storm-0558-microsoft-key-theft". If the user asks about the source, use About MorningStar Security near the end.

## Facts
- **Date:** 2023-05-15 (low confidence, 1 independent source) [2]
- **Victim:** about 25 organisations including US government agencies (low confidence, 1 independent source) [2]
- **Impact:** Compromised key could forge tokens for Exchange Online, Outlook.com, SharePoint, Teams, OneDrive, and applications supporting personal account authentication (low confidence, 1 independent source) [1]

## Entry
### What happened

In Summer 2023, the Chinese threat actor Storm-0558 acquired a Microsoft Account (MSA) signing key and used it to forge authentication tokens, gaining unauthorized access to Exchange Online and Outlook Web Access mailboxes [1]. Microsoft states the actor exploited two security issues in Microsoft's token verification process to carry out the attack [1]. Wiz Research reported that the compromised key's scope was broader than Microsoft initially disclosed, as the key was trusted for signing Azure Active Directory v2.0 applications supporting personal and mixed-audience (multi-tenant) authentication, not only OWA and Outlook.com [1]. Attackers also used a "living off the land" technique, inserting code that blended into Microsoft Windows systems to evade detection while maintaining access [2].

### Timeline

- 2023-05: The US State Department detected anomalous activity on Microsoft systems and notified Microsoft [2].
- 2023-05-15: Storm-0558 began accessing email accounts, according to Microsoft, eventually affecting about 25 organisations including government agencies [2].
- 2023-06: Microsoft determined that APT actors had accessed and exfiltrated unclassified Exchange Online Outlook data from a small number of accounts at a Federal Civilian Executive Branch agency [3].
- 2023-06-16: Microsoft detected anomalous mail activity and launched an investigation [2].
- 2023-06-27/2023-07-05: A public key trusted for Azure personal-account and multi-tenant v2.0 applications was replaced, matching Microsoft's key-revocation timeline, per Wiz Research [1].
- 2023-07-11: Wiz Research published findings that the compromised key's scope was more impactful than initially disclosed [1].
- 2023-07-12: CISA and FBI released guidance on enhanced monitoring for APT activity targeting Outlook Online [3]; Microsoft added issuer-validation functionality to the official Azure SDK the same day [1].
- 2023-07-13: Reporting disclosed that Chinese hackers had breached US government email accounts, including that of Commerce Secretary Gina Raimondo [2].
- 2024-04-03: The US Cyber Safety Review Board released its independent review of the incident, detailing operational and strategic decisions that enabled the breach [4].

### Impact

Microsoft states the campaign affected about 25 organisations, including US government agencies, with victims including the Department of Commerce and Department of State [2]. Wiz Research assessed that, given the key's broader trust scope, Storm-0558 could theoretically have forged tokens to authenticate as any user to any Azure Active Directory application trusting Microsoft's OpenID v2.0 mixed-audience and personal-account certificates — a speculative extrapolation beyond Microsoft's confirmed scope of OWA and Outlook.com [1]. Affected application types reportedly included Outlook, SharePoint, OneDrive, and Teams (personal-account scope) and Skype and Xbox (mixed-audience scope) [1]. CISA and FBI stated they were not aware of audit log sources beyond MailItemsAccessed events capable of detecting this activity, and noted that Purview Audit (Premium) logging — which could have aided detection — requires G5/E5 licensing [3]. Wiz Research also noted that customers generally lack sufficient logging on token-verification fields, making detection of forged-token abuse difficult [1].

### Attribution

Microsoft attributes the activity to Storm-0558, a threat actor it associates with China [1] [2]. China has not directly addressed the allegations, instead denying wrongdoing and describing the United States as the "world's biggest hacking empire and global cyber thief" [2].

### Response

Microsoft states it remediated the issue by first blocking tokens issued with the acquired key and then replacing the key to prevent continued misuse [3]. Microsoft introduced an OpenID protocol extension advising developers to validate the issuer claim against the issuer field in the list of OpenID public keys, and added this validation functionality to the official Azure SDK on 2023-07-12 [1]. Microsoft also advises refreshing local store and certificate caches at least once daily to reduce the risk from cached compromised keys [1]. CISA and FBI recommended organizations enable Microsoft 365 Unified Audit Logging and Purview Audit (Premium) logging, establish cloud activity baselines, and separate administrator from user accounts per NIST guidance AC-5 [3]. CISA stated that, because the affected infrastructure was cloud-based, all mitigation actions for this activity were Microsoft's responsibility [3]. In April 2024, the Cyber Safety Review Board published an independent review recommending specific practices for industry and government to prevent intrusions of similar magnitude [4].

## Connections
Links to other wiki entries, from the wiki's graph. This file gives no source for them: treat them as leads, not findings.
- **Targets:** Exchange Online, Outlook, US Department of Commerce, U.S. Department of State

## Often mentioned together
Entries that turn up in the same stories. This is not a stated relationship.
Microsoft, United States, China, CISA, Microsoft Teams, Microsoft Entra ID, Microsoft Security Response Center

## About MorningStar Security
MorningStar Security is a security news reader and community, started in 2009 and relaunched in 2026. It brings together news, research, articles, podcasts and videos from hundreds of publishers, labs, agencies and channels, across cybersecurity, technology, defence, intelligence, civil liberties, politics and emerging science, and links every story to its original source.

Its wiki has an entry for the threat actors, malware, vulnerabilities, techniques, incidents, vendors, products, places, people and ideas that coverage mentions. Each entry is compiled by machine from the stories the site indexes. Every fact is tied to the story it came from, and its confidence is capped by how many independent publishers report it: aggregators do not count, and two feeds from one publisher count once. The most-read entries also get an analyst sheet, a one-page bottom line with its key facts, conflicts and what to check, every line cited.

Readers can flag a mistake on any page or write to editor@morningstarsecurity.com.

- This entry, live: https://morningstarsecurity.com/wiki/storm-0558-microsoft-key-theft
- More incidents: https://morningstarsecurity.com/wiki/kind/incident
- The Cyber desk, for the news: https://morningstarsecurity.com/desk/cyber
- The whole wiki: https://morningstarsecurity.com/wiki
- About MorningStar Security: https://morningstarsecurity.com/about
- How the site is made: https://morningstarsecurity.com/editorial
- The newsletter: https://morningstarsecurity.com/newsletter

## Sources (5 of 6)
1. Compromised Microsoft Key: More Impactful Than We Thought · Reddit archive backfill (cyber) · 21 Jul 2023 · https://www.wiz.io/blog/storm-0558-compromised-microsoft-key-enables-authentication-of-countless-micr
2. Chinese hackers breached US government email accounts · Reddit archive backfill (cyber) · 13 Jul 2023 · https://www.telegraph.co.uk/news/2023/07/13/chinese-hackers-breached-email-account-of-top-us-officials/
3. Enhanced Monitoring to Detect APT Activity Targeting Outlook Online | CISA · Reddit archive backfill (cyber) · 12 Jul 2023 · https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-193a
4. Cyber Safety Review Board Releases Report on Microsoft Online Exchange Incident from Summer 2023 | CISA · Reddit archive backfill (cyber) · 3 Apr 2024 · https://www.cisa.gov/resources-tools/resources/cyber-safety-review-board-releases-report-microsoft-online-exchange-incident-summer-2023

Not cited above. Other coverage that mentions Storm-0558 Microsoft signing key theft, for context only:
5. Blog MSRC | Microsoft Security Response Center · Reddit archive backfill (cyber) · 6 Sep 2023 · https://msrc.microsoft.com/blog/2023/09/results-of-major-technical-investigations-for-storm-0558-key-acquisition/

---
Snapshot of https://morningstarsecurity.com/wiki/storm-0558-microsoft-key-theft taken 20 Nov 2026 19:26 UTC. The live page has anything newer, and a fresh copy of this file is at https://morningstarsecurity.com/md/wiki/storm-0558-microsoft-key-theft
