On Friday, May 12, a piece of ransomware called WannaCry (also spelled WannaCrypt or WanaCrypt0r) spread across the world in a matter of hours. Hospitals in the UK's National Health Service turned away patients and cancelled appointments. Factories stopped production lines. Businesses large and small came in to find a red ransom screen demanding Bitcoin in exchange for their files.
The frustrating part is that most of this was preventable. The Windows flaw WannaCry used had been fixed by Microsoft back in March. The computers that got hit were, for the most part, the ones that had not installed that update. That makes this a good week to talk about something unglamorous but important: patching.
What actually happened
Most ransomware arrives the same way: someone opens a bad attachment or clicks a bad link, and one computer gets encrypted. WannaCry was different. Once it got onto one machine, it acted like a worm — it scanned the network for other Windows computers and infected them on its own, with nobody clicking anything.
It did that by abusing a weakness in SMB version 1, an old file-sharing protocol that Windows has carried around for decades. The exploit, nicknamed EternalBlue, was among a batch of hacking tools reportedly taken from the U.S. National Security Agency and dumped online by a group calling itself the Shadow Brokers in April. Criminals took that tool and bolted ransomware onto it.
The spread slowed over the weekend after a security researcher noticed the malware checked for a particular web address and registered it, which acted as an accidental "kill switch." That was luck, not a defense plan.
Microsoft fixed this in March
Microsoft released the fix, known as security bulletin MS17-010, as part of its regular March updates. Any supported version of Windows — Windows 7, Windows 8.1, Windows 10, and the server versions — that had those updates installed was protected from the worm-style spread.
What got hit hardest were machines that had not been updated, plus a lot of computers still running Windows XP and Windows Server 2003, which Microsoft stopped supporting years ago. The situation was serious enough that Microsoft took the unusual step of releasing an emergency patch for those retired systems over the weekend. That is a rare exception, and nobody should plan around it happening again.
The difference between the businesses that had a bad Monday and the ones that did not was mostly whether a two-month-old update had been installed.
Why small businesses should care
This is not just a big-organization problem. WannaCry did not pick targets; it scanned for any vulnerable machine it could reach. A ten-person office with one unpatched PC and an open file share is just as reachable as a hospital.
We often see the same patterns in small offices that made WannaCry so damaging:
- Updates that get postponed forever. Someone clicks "remind me later" for months, or updates were turned off years ago because one of them broke a printer driver.
- An old PC nobody wants to touch. The XP machine that runs the label printer, the old server in the closet, the front-desk computer that "just works."
- A flat network. Every computer can talk to every other computer, so one infection can reach everything, including the server.
- Backups that are connected all the time. If the backup drive is plugged in and mapped as a drive letter, ransomware can encrypt it right along with everything else.
Patch management is not optional anymore
Patching sounds simple: install the updates. In practice, a small office usually has no one whose job it is to make sure every computer and server actually got every update, that nothing failed quietly, and that the machine in the back room did not fall off the list. That is what patch management means — not just turning on Windows Update, but verifying it worked across every device.
A proper process looks like this: updates are approved and pushed on a schedule, a report shows which machines are missing what, failures get investigated, and critical security fixes like MS17-010 get fast-tracked instead of waiting for the next convenient month. That is a core piece of the managed IT services we provide, because it is exactly the kind of routine work that slips when everyone is busy running the business.
Turn off SMBv1
SMB version 1 is roughly 30 years old. Modern Windows uses SMB 2 and 3 for file sharing, and in most offices nothing actually needs version 1 anymore. Microsoft itself recommends disabling it. The exceptions tend to be very old devices — some older copiers and scan-to-folder setups, some network storage boxes, and XP-era machines. It is worth finding those before you flip the switch, but for most businesses turning SMBv1 off is a quick win that removes the exact doorway WannaCry walked through.
While you are at it, make sure SMB file sharing is never exposed directly to the internet. Your firewall should be blocking it from the outside.
Backups: your last line of defense
Patching keeps ransomware out. Backups are what save you if it gets in anyway. The businesses that shrug off a ransomware infection are the ones that can wipe the affected machines and restore yesterday's files without paying anybody. A few basics:
- Keep at least one copy of your backups offline or offsite, where ransomware on your network cannot reach it.
- Test restores regularly. A backup you have never restored from is a hope, not a plan.
- Back up the server and the places people actually save things — including desktops, if that is where files end up.
What to do this week
- Confirm every Windows PC and server has the March 2017 security updates (MS17-010) installed. Check, do not assume.
- Find any Windows XP, Vista or Server 2003 machines. Apply Microsoft's emergency patch, then make a plan to retire them.
- Disable SMBv1 where nothing depends on it.
- Make sure your firewall blocks SMB (port 445) from the internet.
- Verify you have a recent backup that is disconnected from the network, and test a restore.
- Remind staff to be careful with unexpected attachments — copycat phishing emails always follow a big news story.
WannaCry was loud and fast, but its lesson is old and quiet: keep systems updated, retire what cannot be updated, and keep a backup that ransomware cannot touch. If you are not sure where your office stands on any of those, email us at info@pinellasit.com or use the contact form, and we will help you find out.
