Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Happened in the Change Healthcare Attack?

In February 2024 ransomware against Change Healthcare halted a third of US medical claims processing for weeks and exposed data on roughly 193 million people, after an account without MFA was reused.

Illustration for the cybersecurity term Change Healthcare Attack
Home / Blog / Cybersecurity Terms / What Happened in the Change Healthcare Attack?
17 November 2026

What Happened in the Change Healthcare Attack?

What Happened in the Change Healthcare Attack?

On 21 February 2024, UnitedHealth Group’s Change Healthcare subsidiary disconnected its systems after discovering ransomware on its network. Change Healthcare processes a substantial share of all medical claims in the United States, and the disconnection stopped prescriptions being dispensed, claims being adjudicated, and providers being paid. Small practices went weeks without revenue, some pharmacies reverted to paper, and the incident became the clearest demonstration yet that a payments intermediary can be a single point of failure for an entire sector.

How the Attackers Got In

The entry point was mundane. In testimony to the US Senate Finance Committee on 1 May 2024, UnitedHealth chief executive Andrew Witty confirmed that attackers used stolen credentials to log in to a Citrix remote access portal that was not protected by multi-factor authentication. From there they moved laterally for roughly nine days before deploying ransomware attributed to the ALPHV group, also known as BlackCat. A company of that size had almost certainly completed an access review that should have caught the gap; the control simply had not been applied uniformly.

The criminal side of the story was equally instructive. UnitedHealth paid a ransom of approximately $22 million in bitcoin. The affiliate who had carried out the intrusion then claimed publicly that the ALPHV operators had taken the payment and cut them out, and a second group later extorted the company again over the same stolen data. Payment bought neither silence nor deletion, which is the consistent finding across double extortion ransomware cases.

The Scale of the Data Loss

Notification to the US Department of Health and Human Services initially put the number of individuals affected at 100 million, revised in January 2025 to roughly 193 million — the largest healthcare breach ever recorded in the United States. Exposed data included names, addresses, diagnoses, treatment details, test results, and insurance and financial information. UnitedHealth reported incident costs of around $2.9 billion for 2024, before any consideration of the long tail of litigation.

Why It Matters to a UK Organisation

The specifics are American, but the structure is familiar. UK healthcare has its own concentration risk, demonstrated in June 2024 when a ransomware attack on the pathology provider Synnovis forced London hospitals to postpone thousands of appointments and operations and triggered a national appeal for blood donors. In both cases the compromised organisation was a supplier rather than the care provider, and in both cases clinical services degraded because a commercial dependency failed.

That is squarely a supply chain question, and UK regulation increasingly treats it as one. The NIS Regulations 2018 place duties on operators of essential services and their oversight bodies; the Network and Information Systems framework is being extended; and for financial entities, DORA imposes explicit concentration risk analysis on critical third parties. The practical test is simple and uncomfortable: list the suppliers whose outage would stop you trading within 48 hours, then ask what you would actually do.

Four Controls This Incident Argues For

Rehearsing that last point is cheap compared with discovering the answer during an outage. At Privia Security, we run scenario-based exercises against exactly this kind of dependency failure through our cyber exercise services, and the supplier questions are usually the ones that generate the longest action list.

FAQ – Frequently Asked Questions

Was the Change Healthcare Attack a Zero-Day Exploit?

No. Attackers signed in to a Citrix remote access portal using stolen credentials on an account that lacked multi-factor authentication. No novel vulnerability was required. That is characteristic of large ransomware incidents: valid credentials and exposed remote access account for a far larger share of intrusions than previously unknown software flaws.

Did Paying the Ransom Resolve the Incident?

It did not. UnitedHealth paid roughly 22 million dollars, after which the affiliate who carried out the attack claimed the operators had withheld their share, and a second group extorted the company again over the same data. The stolen records still surfaced, and the notification count eventually reached about 193 million individuals.

Could the Same Thing Happen in the UK?

A comparable pattern occurred in June 2024, when ransomware against the pathology supplier Synnovis disrupted services at major London hospital trusts, forcing cancellations and a national blood appeal. The common factor is dependency on a single commercial processor for a function the sector cannot perform manually at scale.

What Should Boards Take From This Incident?

That supplier concentration is a board-level risk, not a procurement detail. Identify the third parties whose failure would halt operations within days, confirm what recovery they have committed to contractually, test whether a manual process exists, and verify that remote access into your own environment enforces multi-factor authentication everywhere, including on legacy gateways.

Related Terms

You May Be Interested In These

What Is DNP3 Security?

Cybersecurity Terms

17 November 2026

What Is DNP3 Security?

Read More
What Is Path Traversal?

Cybersecurity Terms

17 November 2026

What Is Path Traversal?

Read More