DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRSEC 8-KState AGConfirmed14 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcednation_statehigh sensitivity
Merged incident · 14 filings

CHANGE HEALTHCARE INC. — February 2024 breach

Clustered 14 filings across 11 jurisdictions · filing window Feb 22, 2024 → Nov 1, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

11

Affected · reported

192,700,000

First → last filing

Feb 22, 2024 → Nov 1, 2024

Merge confidence

100%

incident inc_d10c7524ccf548ac · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. Intrusion Feb 12, 2024–Feb 22, 2024, discovered Feb 17, 2024 — the first regulatory filing landed 5 days later (flagged late). 192,700,000 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 6 more. Notifications rolled out on a 253-day schedule across 14 filings beginning Feb 22, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
5days

Discovered → first regulatory filing

Discovery variance
25days

Range of discovered_at dates across filings

Materiality delta
0days

Discovery to SEC materiality determination

SEC filing delay
1days

Materiality determination to SEC 8-K filing

Filing span
253days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksSEC✗ SEC 4-day late · 63dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 159dOregon✗ OR AG >45dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Feb 12, 2024breach begins
Feb 17, 2024discovered · members disagree
notification delay · 5 days
Feb 22, 2024first filing
Nov 1, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. FEB 22SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. APR 24SEC 8-KSEC 8-K noticeno count stated+62d
  3. JUL 19HHS OCRHHS OCR noticestates nationwide total 192,700,000+148d
  4. JUL 29VT AGVT AG noticeno count stated+158d
  5. AUG 1IL AGIL AG noticeno count stated+161d
  6. AUG 2NH AGNH AG noticeno count stated+162d
  7. AUG 2MT AGMT AG notice346,718 MT residents+162d
  8. AUG 3WA AGWA AG noticestates nationwide total 192,700,000+163d
  9. AUG 3CA AGCA AG noticeno count stated+163d
  10. AUG 3OR AGOR AG noticestates nationwide total 250+163d
  11. AUG 3MA AGMA AG notice2,203,808 MA residents+163d
  12. AUG 5SC AGSC AG notice2,688,358 SC residents+165d
  13. SEP 16OR AGOR AG noticeno count stated+207d
  14. NOV 1IL AGIL AG noticemost recent · no count stated+253d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 17, 2024 – Feb 20, 2024
VT AG
Discovered
Feb 17, 2024IL AGFeb 21, 2024SEC 8-K + VT AG + NH AG +5Mar 13, 2024OR AGfilings disagree on discovery
Data types
Credentials · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
HHS OCR + NH AG + MT AG +6
Attack vector
Unauthorized Access· nation-state
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

192,700,000

Sum of filed state slices

8,360,093· 4.3% of stated

96% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US192,700,000
WA3,121,209
SC2,688,358
MA2,203,808
MT346,718

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement2 members

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

253 days

Cadence

~1 / 19.5d

vs. multi-state median

31.6× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.