Cyber case analysis

Change Healthcare ransomware attack (2024)

A ransomware attack on a US healthcare payments and claims processor disrupted pharmacies, hospitals and insurers across the United States for weeks.

190M

people affected, as reported by UnitedHealth in January 2025

Sources are listed with the timeline below.

Documented incident

Change Healthcare ransomware attack (2024)

A ransomware attack on a US healthcare payments and claims processor disrupted pharmacies, hospitals and insurers across the United States for weeks.

Public record
Read the timeline

What happened

Documented timeline

Facts below are taken from official filings, government advisories and the reporting linked as sources. Cybstyx was not involved in this incident.

  1. 21 Feb 2024Change Healthcare, part of UnitedHealth Group's Optum, detected a ransomware attack and disconnected its systems. UnitedHealth disclosed it in a Form 8-K filing the next day.
  2. Feb to Mar 2024Claims processing, prescription services and payments to providers were disrupted nationwide. The attack was attributed to the ALPHV/BlackCat ransomware group.
  3. 1 May 2024In testimony to the US Senate Finance Committee, UnitedHealth's CEO said the attackers used compromised credentials on a Citrix remote-access portal that did not have multi-factor authentication, and confirmed a ransom payment of USD 22 million.
  4. Jan 2025UnitedHealth said the data of about 190 million people had been affected, the largest healthcare data breach reported in the US.

Sources

Facts about the access method and ransom come from the CEO's written and oral testimony to the Senate Finance Committee on 1 May 2024.

What the case teaches

Healthcare security needs identity assurance, vendor access discipline, evidence continuity and response coordination before a crisis becomes business paralysis.

Source basis: Official filings, HHS guidance and US Senate testimony. Educational analysis; Cybstyx was not involved in this incident.

Cybstyx product mapping

  • SecOwl
  • Eidon Identity Mesh
  • Pteron Private Access
  • Tekmerion Evidence Vault
  • Chronyx Threat Timeline
  • Keraunix Response Grid
  • Nyxara DarkWatch

Buyer checklist

Questions to ask after reading this case.

Access

Who can reach sensitive resources?

Map users, vendors, devices, routes and approval logic.

Evidence

Can decisions be proved later?

Preserve timeline, chain-of-custody and admin action context.

Response

Who approves containment?

Define playbooks, rollback and communication paths before a crisis.

Continuity

Can local controls continue?

Validate offline, on-prem and fail-safe behavior.