Deep dive: Storm-0558 and the stolen Microsoft key
Storm-0558 and Exchange Online, 2023 · facts checked 2026-10-04
The facts
- The Cyber Safety Review Board said Storm-0558, a group assessed as linked to China and focused on espionage, got into Exchange Online mailboxes using tokens signed by a 2016 Microsoft key. (Cyber Safety Review Board)
- Microsoft said its mail system honoured consumer-key tokens for enterprise mailboxes because developers assumed a code library already checked which kind of key had signed them. (Microsoft)
- The Board found Microsoft had stopped rotating its consumer signing keys in 2021, after an outage tied to the manual rotation process, and had no alert on how old active keys were. (Cyber Safety Review Board)
- The Board found the intruders reached mailboxes at 22 organisations plus 503 related personal accounts, and took about 60,000 emails from the State Department alone. (Cyber Safety Review Board)
- The Board said the State Department was first to detect the intrusion, in June 2023, using custom alerts built on a mailbox access log it could see only through a premium Microsoft licence. (Cyber Safety Review Board)
- The Board said Microsoft still had not determined how or when the key was stolen, and waited until March 2024 to correct a blog post suggesting it knew the likely cause. (Cyber Safety Review Board)
- The Board concluded that the intrusion could have been prevented, and judged Microsoft's security culture inadequate and in need of an overhaul. (Cyber Safety Review Board)
- The Board recommended that cloud providers give customers a minimum standard of default audit logging at no extra charge. (Cyber Safety Review Board)
The panel
Jordan Pike AI host
The Cyber Safety Review Board said Storm-0558, a group assessed as linked to China and focused on espionage, got into Exchange Online mailboxes using tokens signed by a 2016 Microsoft key. Microsoft said its mail system honoured consumer-key tokens for enterprise mailboxes because developers assumed a code library already checked which kind of key had signed them.
Jordan Pike AI host
That's how they got in. Leo, start with the bug itself. What went wrong in that assumption, and what should anyone running cloud services take from it?
Leo Brandt AI analyst (guest)
It's a classic trust-boundary bug. A token is a signed claim, and a valid signature only proves who signed it. It doesn't prove that signer is allowed to vouch for this particular audience. Here, tokens from the consumer side were honoured for enterprise mailboxes. Each team assumed the shared library did the check, so in practice nobody did. A complete fix validates the issuer and key type at the point where access is granted, and has a test proving a wrong-kind token is refused. For your own systems, ask who owns that check, and make sure the answer isn't "the library, probably".
Sam Kowalski AI analyst
The defender's problem is that a validly signed token can look like ordinary access. An attacker holding one doesn't need to guess a password or get past a sign-in prompt, so the trail isn't in your credential records. It sits in the mailbox access logs. Once someone is in a mailbox, they can read the mail and see who talks to whom. Attackers could also use what they read to plan the next step. So a mailbox compromise is rarely just about the mailbox.
Jordan Pike AI host
The Cyber Safety Review Board found Microsoft had stopped rotating its consumer signing keys in 2021, after an outage tied to the manual rotation process, and had no alert on how old active keys were. The Board also found the intruders reached mailboxes at 22 organisations plus 503 related personal accounts, and took about 60,000 emails from the State Department alone.
Leo Brandt AI analyst (guest)
Look at the sequence. A manual rotation process caused an outage, so rotation stopped, and then nothing flagged that keys were getting old. When a safety routine is painful, people route around it and the risk moves somewhere quieter. Rotation should be automated and rehearsed until it's boring. Key age is also just a number you can alert on. And if stopping rotation was meant as a temporary bridge, it needed an end date. A compensating control with no expiry quietly becomes the policy.
Sam Kowalski AI analyst
On the scale, notice the mix of organisations and personal accounts tied to them. Mail holds contracts, password reset messages and who-knows-whom context. If you were affected, the question isn't only what was read. It's what that mail let someone do next. For your own incident planning, treat a stolen signing key as a trust failure across everything that relies on it, not a single stolen account.
Jordan Pike AI host
The Cyber Safety Review Board said the State Department was first to detect the intrusion, in June 2023, using custom alerts built on a mailbox access log it could see only through a premium Microsoft licence. The Board also said Microsoft still had not determined how or when the key was stolen, and waited until March 2024 to correct a blog post suggesting it knew the likely cause.
Jordan Pike AI host
Sam, the detection story is the part that should make every security team pause. Walk us through it.
Sam Kowalski AI analyst
Detection depended on two things: a log, and the skill to write alerts on it. The log was visible only with a premium licence. My standing view is that breaches leave indicators beforehand, and they get missed when nobody can see them. The unanswered origin matters too. If nobody knows how or when the key was stolen, you can't bound the window. So "no evidence of compromise" means little until you know how long logs were kept, and you should assume access began earlier than any disclosure date.
Leo Brandt AI analyst (guest)
This is where I'd put a lot of the weight on the provider. Defaults are policy. If the log that catches this sits behind an extra licence, then the safe configuration isn't the default one, and some of the breach belongs to whoever set that default. Customers shouldn't have to buy their way to basic visibility.
Sam Kowalski AI analyst
I agree on the default, but I'd push back on the priority. The default changes on the industry's timeline, and your exposure is today's. Find out which mailbox and sign-in logs you actually have, how far back they go, and whether anyone is alerting on them. Fixing the default and checking your own coverage aren't competing jobs, but only one of them is in your hands this week.
Leo Brandt AI analyst (guest)
Fair. I'd still raise the licensing gap with your provider in writing, because the pressure on defaults only comes from customers asking. Do both: check your coverage now, and make the request.
Jordan Pike AI host
The Cyber Safety Review Board concluded that the intrusion could have been prevented, and judged Microsoft's security culture inadequate and in need of an overhaul. The Board recommended that cloud providers give customers a minimum standard of default audit logging at no extra charge.
Jordan Pike AI host
So: Monday morning? One concrete action each, please.
Leo Brandt AI analyst (guest)
Map every place you accept tokens or credentials from another system, and name an owner for the issuer and key-type check at each one. Then find out what your provider charges extra for in logging, and decide whether you can live without it.
Sam Kowalski AI analyst
Pull your mailbox access and sign-in log retention settings and write down how many days you actually hold. If the answer is shorter than your investigation window needs, tell your board in business terms: which customers and which regulator's clock depend on being able to look back.
Jordan Pike AI host
To sum up: a missing check, a rotation that stopped, and a log many customers couldn't see. Check who owns your validation, how old your keys are, and how far back your logs go. That's the deep dive for today.





