Ransomware examples: famous attacks and their lessons
Key takeaways
- WannaCry hit at least 81 of 236 NHS trusts, and patch alerts had been issued without any way to verify local compliance.
- The Change Healthcare attackers entered a Citrix portal using compromised credentials on a system that lacked multifactor authentication, then deployed ransomware nine days later.
- Check ransomware statistics carefully, because the FBI's IC3 figures count reported complaints and losses, not every attack or the full economic cost.
- After an attack, disconnect infected devices without powering them down, preserve evidence, and restore services in priority order while validating the recovered data.
Ransomware attacks can shut down essential services, expose sensitive information, and force organizations to rebuild systems under pressure. Famous incidents such as WannaCry, Colonial Pipeline, Kaseya, and Change Healthcare show why ransomware protection must combine prevention, containment, and tested recovery—not simply antivirus software. This guide examines documented attacks, clarifies the evidence around Bartow County and Chickasaw County, and turns their lessons into practical decisions for business leaders and IT teams. (nao.org.uk)
What do famous ransomware attacks teach us?
Famous ransomware attacks teach three connected lessons: prevent unauthorized access, limit what an intruder can reach, and prepare to restore essential services safely. Patching addresses exploitable weaknesses; strong authentication protects accounts; segmentation restricts movement; and tested backups support recovery. None replaces the others, because an incident can involve both disrupted operations and stolen information. (nccoe.nist.gov)
The useful question is not whether your organization resembles a headline victim. It is whether you share a dependency: remote access, a trusted technology provider, an aging application, or a business process that stops when one system disappears. Use the examples below as prompts for examining those dependencies rather than as predictions of exactly how your next incident will unfold.
Encryption, data theft, and destructive attacks
Ransomware traditionally encrypts files and demands payment for decryption. Double extortion adds another threat: attackers steal information and threaten to publish it. Some extortion incidents involve data theft without encryption, so restoring files does not necessarily resolve the privacy or confidentiality problem. (cisa.gov)
A ransomware-looking incident can also be destructive malware. NotPetya displayed a ransom demand, but its design did not provide a workable recovery path through payment. That distinction matters because a ransom note is evidence of an attacker's message—not proof that the attacker can repair the damage. (justice.gov)
For planning purposes, keep three outcomes separate:
- Availability: Can employees and customers use essential systems?
- Confidentiality: Has someone accessed or copied sensitive information?
- Integrity: Can you trust the accuracy and completeness of recovered records?
These are different recovery questions. NIST's data-integrity guidance emphasizes that getting data back is insufficient unless organizations can trust what they recover. (csrc.nist.gov)
Five famous ransomware examples and their lessons
The following cases illustrate different failure paths, from unpatched systems to compromised credentials and trusted management software. They are not a ranking of the biggest or most expensive attacks. Each is useful because it connects a documented event with a practical question your organization can investigate.
WannaCry: patching warnings need verified follow-through
WannaCry disrupted the NHS in England on May 12, 2017. The National Audit Office found that at least 81 of 236 trusts were affected, alongside hundreds of other NHS organizations. Thousands of appointments and operations were canceled, demonstrating how a technical incident can interrupt frontline services. (nao.org.uk)
The audit identified an important governance gap. NHS Digital had issued critical patching alerts in March and April 2017, but the Department of Health had no formal mechanism before the attack for assessing whether local organizations had complied. Sending guidance and confirming implementation were not the same thing. (nao.org.uk)
The lesson: Treat patching as a verified process, not a notification exercise. Ask for evidence showing which assets received an update, which failed, and which require an approved exception. A dashboard that reports deployment attempts should not be mistaken for proof that every exposed system is protected.
For your next review, ask: Who owns each unsupported application? Who accepts the risk when patching is delayed? Can the team demonstrate the actual patch state of critical systems? These questions translate WannaCry's governance lesson into an actionable assessment rather than another reminder to “keep software updated.”
NotPetya: trusted software and internal access can spread destruction
NotPetya began its worldwide attack on June 27, 2017. U.S. prosecutors described its delivery through the update infrastructure associated with the Ukrainian accounting application M.E.Doc. Despite its ransom demand, the malware was designed so that victims could not recover their files by paying. (justice.gov)
Microsoft's investigation also showed why patching alone was not a complete defense. The malware exploited vulnerabilities addressed by MS17-010, but it could also harvest credentials and use other techniques to traverse networks. A patched computer was therefore not automatically safe from every propagation method. (microsoft.com)
The lesson: Examine the privileges and connections available to trusted software, not just whether it comes from a legitimate supplier. Consider what an application can execute, which credentials it can encounter, and which other environments it can reach. Network segmentation and restricted administrative access are complementary controls because they constrain the consequences of an initial compromise. (hhs.gov)
A useful exercise is to choose one widely deployed application and map its permitted access. If that software became hostile tomorrow, which business services would remain outside its reach? The answer gives your team a concrete starting point for containment planning.
Colonial Pipeline: an IT incident can become an operational crisis
On May 7, 2021, Colonial Pipeline proactively shut down its pipeline system in response to a ransomware attack. The FBI attributed the compromise to DarkSide ransomware. The Department of Energy subsequently coordinated with industry and government partners to support restoration and mitigate fuel-supply impacts. (energy.gov)
The Department of Energy reported that Colonial announced the restart of its entire pipeline system on May 13, 2021. The important distinction is that an operational shutdown followed a ransomware incident; that does not, by itself, establish that ransomware encrypted pipeline control equipment. Avoid turning operational impact into an unsupported claim about every affected technology. (energy.gov)
The lesson: Business continuity planning should identify the digital dependencies behind physical operations. Billing, scheduling, communications, and administrative systems deserve attention alongside production equipment. CISA's guidance recommends documenting network interdependencies and separating IT from operational technology. (cisa.gov)
Ask operations leaders to describe the circumstances under which they would pause a service for safety or uncertainty. Then identify the information they would need to restart it confidently. That discussion is more useful than assuming that keeping industrial equipment uninfected guarantees uninterrupted operations.
Kaseya: management tools concentrate downstream risk
On July 2, 2021, attackers used Kaseya VSA software to distribute ransomware through managed service providers to downstream organizations. The U.S. National Counterintelligence and Security Center described the attack as leveraging a fake update. The incident illustrates how a compromise in a management platform can affect organizations beyond the original software provider. (dni.gov)
Kaseya's technical account described exploitation of vulnerabilities in its on-premises VSA product and documented the deployment of a ransomware payload. The company released a compromise-detection tool on July 3 while preparing remediation and restoration. Those details make this a management-platform compromise, not simply an ordinary malicious email reaching many unrelated businesses. (helpdesk.kaseya.com)
The lesson: Treat remote-management systems and provider access as high-impact trust relationships. Maintain an inventory of third parties, assign internal owners, restrict privileges, and establish rapid incident-notification expectations. The FBI specifically recommends reviewing third-party access and disabling unused accounts. (fbi.gov)
When reviewing a provider, ask for a practical walkthrough: How would you suspend its access during an emergency? Who can authorize that decision? Which services would stop? A contract is useful, but your team also needs an executable containment procedure.
Change Healthcare: one authentication gap can expose a critical dependency
In testimony prepared for a May 1, 2024, congressional hearing, UnitedHealth Group CEO Andrew Witty described attackers entering a Change Healthcare Citrix portal on February 12 using compromised credentials. The portal lacked multifactor authentication. According to the testimony, attackers moved laterally, exfiltrated data, and deployed ransomware nine days later. (d1dth6e84htgma.cloudfront.net)
Witty described disruption across the healthcare system and a response focused on securing systems, maintaining patient access to care and medication, and supporting providers financially. Change Healthcare's role in information, claims, and payment flows made the consequences extend beyond its own employees and systems. (d1dth6e84htgma.cloudfront.net)
The lesson: Verify authentication on every actual access path, including older portals and systems inherited through organizational change. A company-wide MFA policy is not evidence that a particular application enforces it. CISA recommends phishing-resistant MFA and warns that authentication methods differ in their resistance to attack. (cisa.gov)
For a practical review, request an application-by-application exception list rather than a single enrollment percentage. Ask how exceptions are discovered, who approves them, and what happens when a business-critical system cannot support the required protection.
Local incidents: separating confirmed facts from search claims
Local cyber incidents require the same evidence standards as famous attacks. Confirm the affected organization, jurisdiction, incident date, and source before assigning a ransomware label. The Bartow County and Chickasaw County examples are especially useful because their records support different conclusions about encryption and data exposure. (wbhfradio.org)
Bartow County ransomware attacks 2024–2026: what is established
Searches for “bartow county ransomware attacks 2024-2026” should not be treated as evidence of repeated confirmed attacks across those years. The district's documented October 2024 statement establishes a five-day service disruption and an attempted unauthorized external access to part of the Bartow County School System's information systems. It does not establish a series of incidents spanning 2024 through 2026. (wbhfradio.org)
In that statement, reproduced in full by WBHF on October 18, 2024, the district said it was working with outside experts to determine whether information had been accessed or compromised. It committed to notifying affected people if sensitive personal information was impacted. The statement did not confirm encryption, identify an attacker, or establish a ransom payment. (wbhfradio.org)
The lesson: Keep confirmed disruption separate from unresolved technical findings. A responsible incident update can explain service availability, investigation status, and next steps without guessing about data theft. When researching later developments, look for a dated district notice or other authoritative finding; a retrospective article's publication year is not necessarily a new attack date.
Chickasaw County ransomware and data-breach searches
For readers searching “chickasaw county ransomware data breach cyber attacks,” the relevant primary record here concerns Chickasaw County, Iowa, on or about February 15, 2020. County board minutes state that ransomware encrypted multiple servers and user workstations. The county engaged legal counsel, which arranged a forensic investigation. (chickasawcounty.iowa.gov)
The recorded memorandum said investigators found no evidence that attackers accessed file contents or attempted to take data from the network. It concluded that personally identifiable information had not been compromised and that the incident did not trigger notification requirements. Those were findings for that incident—not a universal rule about ransomware or breach obligations. (chickasawcounty.iowa.gov)
The lesson: Describe encryption and data theft separately. The record supports calling this a ransomware incident, but not presenting it as a confirmed theft of personal information. Preserve the jurisdiction and date so readers do not confuse this county with another organization sharing the Chickasaw name.
Reading ransomware statistics without misleading yourself
The FBI's 2025 IC3 Annual Report states that IC3 received more than 3,600 ransomware complaints, with reported losses exceeding $32 million. These are complaints and losses reported through that channel—not a complete census of attacks or the total economic cost of ransomware. (fbi.gov)
The report explains that adjusted ransomware losses generally exclude lost business, time, wages, files, equipment, and third-party remediation services. Some complainants report no loss amount, and the figures do not include incidents reported directly to FBI field offices rather than IC3. These limitations are essential context, not minor footnotes. (fbi.gov)
Before using ransomware statistics in a budget proposal, check:
- The unit: Complaints, affected organizations, exposed records, and attacker claims are different measures.
- The period: A full calendar year is not directly comparable with an incomplete year.
- The population: A U.S. reporting channel is not a worldwide count.
- The cost definition: Ransom payments and total recovery costs answer different questions.
- The evidence: Ask whether the dataset counts verified incidents or unverified allegations.
Use statistics to frame the problem, then base your own priorities on service dependencies, data sensitivity, and demonstrated control gaps. Avoid presenting an industry average as a reliable forecast for one organization.
Building ransomware prevention around the attack path
Effective ransomware prevention combines controls that address entry, spread, detection, and recovery preparation. NIST's example architecture brings together asset inventories, vulnerability management, network protection, backups, logging, and integrity monitoring. Its central point is defense in depth: a missed threat at one stage should not leave every later stage unprotected. (nccoe.nist.gov)
Protect identities and reduce unnecessary access
Prioritize phishing-resistant MFA for remote access, email, administrative accounts, and critical applications. CISA notes that some MFA methods remain vulnerable to phishing or approval-fatigue attacks. Plan deployment around actual applications and recovery workflows, not just whether users have registered an authenticator. (cisa.gov)
Include onboarding and account recovery in that review. Microsoft's published implementation approach addresses stronger authentication, temporary access, workload identities, and identity verification during onboarding. This is a useful reminder that protecting the normal login while leaving reset procedures weak creates an incomplete identity program. (learn.microsoft.com)
For an internal assessment, ask the team to demonstrate one ordinary login, one administrator login, and one account-recovery request. Record any route that avoids the intended controls. Give each exception an owner and an agreed decision rather than allowing it to disappear into a general project backlog.
Patch exposed systems and make reporting easy
The FTC recommends keeping security current, installing patches and updates, and teaching employees how to recognize phishing and other infection routes. Its guidance also identifies server vulnerabilities and remote-access protocols as potential entry points. Training therefore belongs alongside technical maintenance, not in place of it. (ftc.gov)
Make your review concrete. Select an internet-facing service and trace its ownership, update process, exception history, and escalation route. Then ask an employee to demonstrate how they would report an unexpected login prompt or suspicious attachment. A written process is only useful if the people involved can follow it.
Limit spread and preserve investigative visibility
Segmentation can restrict ransomware's lateral movement and help isolate critical systems and backups. HHS guidance describes benefits including more granular access control and improved monitoring within segments. Design those boundaries around required business communication rather than assuming every internal device should reach every other device. (hhs.gov)
Centralized logs help investigators reconstruct activity across authentication, endpoints, networks, remote access, and cloud services. The FBI recommends protected log storage, synchronized clocks, and exercises that test whether activity for a user or server can actually be reviewed. Monitoring needs an operational owner, not merely a purchased platform. (fbi.gov)
A useful tabletop question is: If one employee laptop were compromised, what evidence would show where its account was used next? Ask for a demonstration using retained logs. This turns an abstract claim about “visibility” into something the organization can verify.
Protect backups before you need them
Back up the environment needed to deliver services, not only selected documents. The FTC recommends preserving important files and a full environmental backup, including programs and the operating system, on storage disconnected from the network. Backup scope should reflect what must be rebuilt to resume work. (ftc.gov)
NIST's asset-protection guidance includes backup data, configuration files, logs, and golden images among important resources. Use that broader perspective when reviewing coverage: an application database may be available while a missing configuration or installation dependency still prevents restoration. (nvlpubs.nist.gov)
For your next test, choose one essential service and restore it in an isolated environment. Ask its business owner to complete a representative task, record the obstacles, and update the recovery instructions. Treat the test as a search for missing dependencies, not a ceremony to confirm that everything works.
How should ransomware recovery work after an attack?
Ransomware recovery should contain the compromise, preserve evidence, establish its scope, remove attacker access, and restore trusted systems in business-priority order. It is not simply copying files back. CISA's response guidance emphasizes clean recovery environments, prioritized restoration, and avoiding reinfection when systems reconnect. (cisa.gov)
Contain the incident without destroying useful evidence
The FTC advises immediately disconnecting infected devices from the network without powering them down, because shutdown can lose useful investigative information. Experienced internal staff or outside specialists should investigate access, affected systems, and the weakness that enabled the intrusion. Coordinate containment rather than asking employees to improvise repairs. (ftc.gov)
A practical response sequence should cover these decisions:
- Activate leadership and technical response. Establish who can authorize isolation, emergency spending, and operational changes.
- Restrict affected access. Isolate impacted systems and address compromised accounts, sessions, or remote-access paths.
- Preserve evidence. Retain relevant logs, ransom notes, system images, and other investigative material where feasible.
- Determine scope. Investigate earlier activity and possible data theft, not just the systems displaying encryption.
- Prepare clean restoration. Rebuild and reconnect according to critical-service priorities, addressing persistence and security gaps.
These decisions should be coordinated by the response team; their exact order can overlap as evidence emerges. CISA's checklist provides detailed containment, investigation, rebuilding, and recovery actions. (cisa.gov)
Restore services and validate the recovered data
NIST emphasizes both rapid recovery and confidence in the accuracy of restored information. Use that principle to define acceptance criteria before declaring a service operational. A running server is not enough if records are incomplete, transactions cannot reconcile, or the application produces unreliable results. (csrc.nist.gov)
For example, a payroll restoration test could require a designated business owner to check employee records, review a sample calculation, and confirm that the required approval workflow functions. This is an illustrative test design, not a claim that every payroll system needs the same procedure. Adapt acceptance checks to the service and its consequences.
Recovery planning should also identify priorities, realistic test scenarios, and measures for improvement. NIST recommends learning from both your own incidents and other organizations' experiences. Document actual obstacles during restoration so the next exercise addresses observed weaknesses rather than repeating an easy demonstration. (csrc.nist.gov)
Communicate operational facts and unresolved findings separately
Recovery communication should distinguish service availability from investigation conclusions. Bartow County School System's statement illustrates this separation: it described restoration work while leaving potential information access under investigation. That approach allows useful updates without pretending the technical picture is already complete. (wbhfradio.org)
Prepare a simple update format: services affected, available alternatives, actions recipients should take, and the next expected update. Keep technical speculation out of public messaging. Assign a named approver so urgent communications do not stall while several teams assume someone else owns them.
Ransom payments are not a recovery guarantee
The FBI does not support paying ransomware demands. Payment does not guarantee that an organization will get its data back, and it encourages further criminal activity. Victims should contact their local FBI field office or report through IC3 rather than treating negotiation as a substitute for incident response. (fbi.gov)
Government guidance also identifies risks including repeat targeting, additional demands, and failure to receive promised decryption keys. Evaluate restoration options and involve appropriate technical, executive, insurance, and legal advisers. Do not mistake an attacker's promise for verified recovery capability. (fbi.gov)
Decryption assistance may sometimes be available through law enforcement. For example, the Justice Department's February 20, 2024, LockBit disruption announcement encouraged victims to contact the FBI so authorities could determine whether affected systems could be decrypted. Availability depends on the case; there is no universal decryptor. (justice.gov)
Turn the lessons into a measurable readiness review
Use this guide to commission a small set of demonstrations rather than another broad reassurance that security is “covered.” Ask each owner to provide evidence, identify unresolved dependencies, and record the next decision. The following checklist is a suggested review format, not a claim of certification or complete protection.
| Review area | Evidence to request | Decision to record |
|---|---|---|
| Authentication | Demonstration of remote and administrator access | Which exceptions require remediation? |
| Patching | Actual status of a critical exposed system | Who owns failed or deferred updates? |
| Provider access | Inventory and emergency suspension walkthrough | Who can disconnect a provider? |
| Containment | Diagram of permitted access between critical environments | Which unnecessary connections should close? |
| Recovery | Isolated restoration with business-owner validation | Which dependencies or instructions are missing? |
| Communications | Exercise using an approved incident-update template | Who approves the next public update? |
Keep the exercise bounded enough to complete, but choose a service important enough that the result matters. Give every unresolved issue an owner, a due date, and a method for verifying completion. Revisit the same service after changes so progress means demonstrated capability rather than a longer list of planned improvements.
The lasting lesson is not to copy a famous victim's response. It is to turn documented failures into questions your organization can answer with evidence. Start with one essential service, prove how it is protected and restored, and use the gaps you discover to set the next priorities.
Related guides
- Does cloud backup protect against ransomware?
- Is end-to-end encryption safe? What it does not cover
Sources
- Investigation: WannaCry cyber attack and the NHS - NAO press release
- nccoe.nist.gov: Index
- cisa.gov: StopRansomware Guide%20508
- justice.gov: Dl
- SP 1800-11, Data Integrity: Recovering from Ransomware and Other Destructive Events | CSRC
- Update on Petya malware attacks
- hhs.gov: Ransomware healthcare
- Colonial Pipeline Cyber Incident | Department of Energy
- cisa.gov: CISA MS ISAC Ransomware%20Guide S508C
- dni.gov: Kaseya%20VSA%20Supply%20Chain%20Ransomware%20Attack
- Incident Overview & Technical Details – Kaseya
- fbi.gov: Ten actions to improve cyber resiliency
- d1dth6e84htgma.cloudfront.net: Witty Testimony OI Hearing 05 01 24 5ff52a2d11
- cisa.gov: Fact sheet implementing phishing resistant mfa 508c
- Bartow County School System Releases Statement Regarding Districtwide Internet Outage | WBHF
- chickasawcounty.iowa.gov: Minutes 11116
- fbi.gov: Ic3report
- Phishing-resistant MFA | Microsoft Learn
- ftc.gov: Cybersecurity
- nvlpubs.nist.gov: NIST.SP.1800 25
- #StopRansomware Guide | CISA
- SP 800-184, Guide for Cybersecurity Event Recovery | CSRC
- fbi.gov: Ransomware
- fbi.gov: Ransomware prevention and response for cisos
- justice.gov: Us and uk disrupt lockbit ransomware variant