EpiSource — January 2025 breach

Clustered 25 filings across 8 jurisdictions · filing window Jun 6, 2025 → Feb 11, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

25 filings

States

Affected · reported

6,725,572

First → last filing

Jun 6, 2025 → Feb 11, 2026

Merge confidence

100%

incident inc_a0171f122f7f4dd2 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 25 regulatory filings. Intrusion Jan 27, 2025–Feb 6, 2025, discovered Feb 6, 2025 — the first regulatory filing landed 120 days later (flagged late); 13 later filings were also flagged late. 6,725,572 individuals reported across the linked filings. Data reported: Government ID, PHI, Identity (basic), and 3 more. Notifications rolled out on a 250-day schedule across 25 filings beginning Jun 6, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

120days

Discovered → first regulatory filing

Discovery variance

272days

Range of discovered_at dates across filings

Filing span

250days

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 >90dCalifornia✗ CA 60-day late · 155dVermont✗ VT AG >45 bdayOregon✗ OR AG >45dTexas✗ TX AG >30dHIPAA✓ HHS notifiedDate basis✓ Clock withheld · confirmation dateFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.