Microsoft Storm-0558: a valid signature was not enough.

What happened?

Historical case. Activity disclosed: July 2023. Source checked: 22 October 2026.

Microsoft reported that Storm-0558 used an acquired consumer signing key to forge tokens and access email. The affected services observed by Microsoft were Outlook Web Access in Exchange Online and Outlook.com.

What caused the weakness?

Consumer and enterprise identities should have different trust boundaries. Microsoft described a token-validation problem that allowed a consumer-key-signed token to be accepted for enterprise mail. A cryptographically valid signature is only one check; the expected issuer and scope also matter.

How was it identified?

A customer reported anomalous mail access on 16 June 2023. Microsoft investigated and identified forged authentication artifacts. Its published response included invalidating the acquired key and strengthening validation.

Microsoft’s initial disclosure and response.

What remains uncertain?

Microsoft’s March 2024 addendum says the route by which key material left the signing environment remains a leading hypothesis. It had not found a crash dump containing that key. Do not repeat the earlier crash-dump explanation as a fully established fact.

Updated investigation, including the addendum.

Make the lesson simple

Give a toy application two fictional issuers: a school library and a school office. Use dummy tokens. Demonstrate that accepting “a signed pass” is too broad; the office must also require its own trusted issuer, audience and permitted purpose.

Then show a rejected cross-boundary request. Keep the test disconnected from Microsoft accounts and production tokens. This is a model of validation, not a reproduction of Microsoft’s incident.