Deep dive: the WannaCry ransomware outbreak
WannaCry, May 2017 · facts checked 2026-10-04
The facts
- CISA said WannaCry spread by exploiting a critical flaw in version 1 of the Windows SMB file-sharing protocol, covered by Microsoft bulletin MS17-010, and urged applying the March 14, 2017 patch. (CISA)
- The National Audit Office said WannaCry, a virus that locks up data on infected machines and demands payment to restore access, was released worldwide on Friday 12 May 2017. (National Audit Office)
- The NAO said at least 81 of England's 236 NHS trusts were affected, along with 603 primary care and other NHS bodies, 595 of them GP practices. (National Audit Office)
- The NAO reported that NHS England identified 6,912 cancelled appointments and estimated over 19,000 in total; officials told the NAO that no NHS organisation paid the ransom. (National Audit Office)
- The NAO said disruption could have been worse, but a cyber researcher activated a kill switch that stopped WannaCry from locking devices. (National Audit Office)
- The NAO found infected organisations were running unpatched or unsupported versions of Windows, and said managing their internet-facing firewalls would have kept them safe whether or not they had patched. (National Audit Office)
- In December 2017 the White House publicly attributed WannaCry to North Korea, saying the UK, Australia, Canada, New Zealand and Japan had seen its analysis and joined in denouncing it. (White House)
- The UK government said WannaCry, which hit 300,000 computers in 150 countries, was in the NCSC's judgement highly likely the work of the North Korean Lazarus Group. (UK government)
The panel
Jordan Pike AI host
The National Audit Office said WannaCry, a virus that locks up data on infected machines and demands payment to restore access, was released worldwide on Friday 12 May 2017. The National Audit Office said at least 81 of England's 236 NHS trusts were affected, along with 603 primary care and other NHS bodies, 595 of them GP practices. The National Audit Office reported that NHS England identified 6,912 cancelled appointments and estimated over 19,000 in total; officials told the NAO that no NHS organisation paid the ransom.
Jordan Pike AI host
CISA said WannaCry spread by exploiting a critical flaw in version 1 of the Windows SMB file-sharing protocol, covered by Microsoft bulletin MS17-010, and urged applying the March 14, 2017 patch. The National Audit Office said disruption could have been worse, but a cyber researcher activated a kill switch that stopped WannaCry from locking devices. The National Audit Office found infected organisations were running unpatched or unsupported versions of Windows, and said managing their internet-facing firewalls would have kept them safe whether or not they had patched.
Jordan Pike AI host
The UK government said WannaCry, which hit 300,000 computers in 150 countries, was in the NCSC's judgement highly likely the work of the North Korean Lazarus Group. The White House attributes WannaCry to North Korea, in a public statement in December 2017, saying the UK, Australia, Canada, New Zealand and Japan had seen its analysis and joined in denouncing it.
Jordan Pike AI host
That's the outline. Let's take it in order: how it got in, how it spread, what stopped it, who is blamed, and what changed for defenders. Sam, start with the way in.
Sam Kowalski AI analyst
The way in, per CISA, was a critical flaw in the old file-sharing protocol. File sharing is a service machines offer to each other, so a flaw there is the kind of thing that lets malware hop from one reachable machine to the next without anyone clicking anything. The part that should sting is the timing: the patch CISA points to was dated March 14, 2017, and the release came in May. The fix existed before the outbreak did.
Rina Takahashi AI analyst
Then the attribution, and I want to be strict about who is claiming what. The UK government says the NCSC judged it highly likely to be the Lazarus Group. That is a confidence statement, not a certainty. The White House goes further and attributes it to North Korea, and says partner governments had seen the analysis and joined in. Those are government claims, and the wording tells you how confident each one is.
Jordan Pike AI host
Sam, the kill switch. The National Audit Office says a researcher activated it and it stopped devices from being locked. Is that the happy ending?
Sam Kowalski AI analyst
It's a lucky break, not a control. Nobody can build a defence plan around an attacker's design choice working in their favour. And the damage was already real: appointments were cancelled and a huge number of organisations were hit before the lock-ups stopped. For responders, the lesson is to work out what was reachable and for how long. If your logs don't go back far enough, you can't say what happened, so you can't claim you were clean.
Rina Takahashi AI analyst
Also worth noting: officials told the NAO that no NHS organisation paid. That's a good outcome, but it only holds if you decided it in advance. Agree your position on paying, and your recovery plan, before the day your systems are locked, not during it. Pressure is the attacker's best friend.
Jordan Pike AI host
The NAO found unpatched or unsupported Windows, and said firewall management alone would have kept them safe. So where do you put your effort first: patching, or the firewall?
Sam Kowalski AI analyst
Patching is the real fix, because it removes the flaw. A firewall rule is a bridge, and a bridge needs an end date, or it becomes the thing everyone forgets until it fails. If an update exists, apply it. If a system can't be updated, that is a risk the board should see in business terms.
Rina Takahashi AI analyst
I'd put the firewall first for anything unsupported, because the NAO says managing internet-facing firewalls would have protected organisations whether or not they had patched. You can't patch what has no patch. Reducing what the internet can reach is fast and doesn't depend on the vendor. I agree with Sam on the end date, though: it buys time, not safety.
Sam Kowalski AI analyst
My action: list every system running unpatched or unsupported Windows, then check which are reachable from the internet or from other parts of your network. Confirm how far back your logs go, so you know what you can and can't say about past activity.
Rina Takahashi AI analyst
Mine: write down your plan for a self-spreading ransomware event before you need it, including who decides about payment and who talks to the regulator. And when you read attribution, note who is making the claim and how confident they say they are.
Jordan Pike AI host
So: Monday morning. Find your unsupported systems, close off what the internet can reach, set an end date on any stopgap, and check your log retention. The patch existed before WannaCry did, and that is the part to remember.





