Change Healthcare ransomware attack disrupts US prescriptions, claims and payments

Attackers using stolen credentials on a remote-access portal without multi-factor authentication deployed ransomware at Change Healthcare, a major US health payments processor. Pharmacies, claims and provider payments were disrupted for weeks; some functions took about nine months to restore.

Status not confirmedLast documented state as of Nov 20, 2024[3]
Security:
Confirmed malicious activity
Started
Feb 21, 2024
Ended
Not documented
Duration
Not computable from sources
Full recovery
Not documented
Geographic scope
United States
Last verified
3 sources

What happened

Systems and services affected
Pharmacy claims processingMedical claimsProvider paymentsClearinghouse services
Kind of failure
Cyberattack
Sector
Healthcare
Provider report
None found
Status and recovery
Status not confirmed (last documented Nov 20, 2024). By April 22, 2024 about 80% of functionality was restored. On November 20, 2024 Change Healthcare confirmed its clearinghouse was back and "the vast majority of its functions" online, with three functions not yet fully restored. We have not found a later statement on those three.[2][3]

Attackers first got in on February 12; ransomware was deployed on the morning of February 21. Restoration ran from March into late 2024.

What caused it?

Root cause: Confirmed

On February 12, attackers "used compromised credentials to remotely access a Change Healthcare Citrix portal" that "did not have multi-factor authentication," moved laterally and exfiltrated data. On February 21 a group calling itself ALPHV or BlackCat deployed ransomware, encrypting Change's systems.[1]

Provider report: None found. UnitedHealth's CEO described the attack in congressional testimony on May 1, 2024. We have not found a full public incident report.[1]

Was it malicious?

Confirmed malicious activity

UnitedHealth Group confirms a ransomware attack by a cybercriminal calling themselves ALPHV or BlackCat. Its CEO testified that he decided to pay a ransom.[1]

How the failure happened

  1. 1TriggerCompromised credentials (Feb 12)
  2. 2FailureLateral movement and data exfiltration
  3. 3SpreadRansomware deployed (Feb 21)
  4. 4ResponseChange cut connectivity to its data centers
  5. Affected4 services and systems

Evidence for each step

  1. 1
    Compromised credentials (Feb 12). Used on a Citrix remote-access portal without multi-factor authentication[1]
    Starting point.
  2. 2
    Lateral movement and data exfiltration[1]
    Led from step 1: Stated in a provider report or official record.
  3. 3
    Ransomware deployed (Feb 21). Change's systems were encrypted[1]
    Led from step 2: Stated in a provider report or official record.
  4. 4
    Change cut connectivity to its data centers. To contain the attack; Change's services went offline[1]
    Led from step 3: Stated in a provider report or official record.

Only steps the sources state are drawn. Affected services are listed under What happened.

Explanation

Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.

Plain language: what happened and why people were affected.

In February 2024, criminals attacked Change Healthcare, a company whose systems move claims and payments between US doctors, pharmacies and health insurers. Pharmacies and healthcare providers had trouble processing prescriptions and getting paid.

The attackers got in with a stolen password to a remote-access system that did not require a second login step. Nine days later they locked Change's computers with ransomware.

Change cut its systems off to stop the spread, then rebuilt them. Most services returned within weeks, but some took about nine months.

Confirmed and unknown

Confirmed

  • Confirmed
    Attackers used compromised credentials to access a Citrix portal that did not have multi-factor authentication.[1]
    Said by: UnitedHealth Group CEO Andrew Witty · Evidence: Official
  • Confirmed
    A cybercriminal calling themselves ALPHV or BlackCat deployed ransomware on February 21.[1]
    Said by: Andrew Witty · Evidence: Official
  • Confirmed
    The CEO decided to pay a ransom.[1]
    Said by: Andrew Witty · Evidence: Official
  • Confirmed
    By March 7, 99% of pre-incident pharmacies could process claims.[1][2]
    Said by: UnitedHealth Group · Evidence: Official

Stated or reported, not confirmed

  • Reported
    Around 100 million people were affected, according to HHS figures.[3]
    Evidence: News
  • Reported
    As of November 20, 2024, three functions were not yet fully restored.[3]
    Evidence: News

Still unknown

  • Whether the three functions still listed as not fully restored in November 2024 have since been restored.

Timeline

Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.

  1. First observedFeb 21, 2024
  2. AcknowledgedNot documented
  3. MitigationMar 7, 2024
  4. RecoveryApr 22, 2024
  5. ResolvedNot documented
  6. Incident reportNone found
  1. Attackers access a Citrix remote-access portal using compromised credentials.[1]
  2. First observed
    Ransomware deployed; UnitedHealth severs connectivity to Change's data centers and contacts the FBI.[1]
  3. Mitigation
    99% of pre-incident pharmacies able to process claims.[1]
  4. Recovery
    About 80% of functionality restored on major platforms.[2]
  5. CEO testifies to Congress about the attack.[1]
  6. Clearinghouse confirmed restored; three functions still not fully restored.[3]

Evidence and sources

Grouped by type of evidence. Numbers match the citations above.

Primary: provider and official sources

Published by the provider or agency itself: incident reports, status records, advisories, statements.

  1. 1.
    Testimony of Andrew Witty, Chief Executive Officer, UnitedHealth Group: Examining the Change Healthcare Cyberattack (opens in a new tab)
    U.S. House Energy and Commerce Committee · Official statement · Published · Accessed
  2. 2.
    UnitedHealth Group Updates on Change Healthcare Cyberattack (opens in a new tab)
    UnitedHealth Group · Official statement · Published · Accessed

Independent reporting

News organizations reporting statements, impact and their own findings.

  1. 3.
    Change Healthcare's clearinghouse services back up and running (opens in a new tab)
    The Register · News · Published · Accessed

Last verified against these sources on Nov 14, 2026.