DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

CF Medical LLC — February 2024 breach

Clustered 8 filings across 8 jurisdictions · filing window Sep 9, 2024 → Sep 30, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

626,396

First → last dated filing

Sep 9, 2024 → Sep 30, 2024

Merge confidence

100%

incident inc_02d0032249fa44ca · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion Feb 14, 2024–Feb 26, 2024, discovered Feb 14, 2024. 626,396 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 21-day schedule across 7 dated filings beginning Sep 9, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
153days

Range of discovered_at dates across filings

Filing span
21days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dMaine⏱ ME AG >30d · 72dDelaware✓ DE credit monitoring dueHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 14, 2024breach begins
Feb 14, 2024discovered · members disagree
Sep 9, 2024first dated filing
Sep 30, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. SEP 1IL AGIL AG noticefiling day not on record · no count stated—
  2. SEP 9IN AGIN AG noticefirst filing · 7,507 IN residentsday 0
  3. SEP 26VT AGVT AG noticeno count stated+17d
  4. SEP 26ME AGME AG noticestates nationwide total 626,396+17d
  5. SEP 26DE AGDE AG noticestates nationwide total 626,396+17d
  6. SEP 26HHS OCRHHS OCR noticestates nationwide total 242,200+17d
  7. SEP 26WA AGWA AG notice540 WA residents+17d
  8. SEP 30SC AGSC AG noticemost recent · 11,199 SC residents+21d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 14, 2024
IN AG
Discovered
Feb 14, 2024IL AGFeb 26, 2024DE AGApr 4, 2024WA AGJul 16, 2024ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + ME AG + WA AG +3
Attack vector
Unauthorized Access
VT AG

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)

626,396

Sum of filed state slices

22,327· 3.6% of stated

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

US626,396
SC11,199
IN7,507
DE2,956
WA540
ME125

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 filing8 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 29, 2026 · at least one link edge was human-adjudicated
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

21 days

Cadence

~1 / 3.5d

vs. multi-state median

3.5× 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.