All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed8 filings · 7 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 8 filings

Outcomes — July 2025 breach

Clustered 8 filings across 7 jurisdictions · filing window Sep 1, 2025 → Oct 24, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

Affected · reported

257,481

First → last filing

Sep 1, 2025 → Oct 24, 2025

Merge confidence

100%

incident inc_b9790f7fa5bb46eb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe social engineering. Intrusion Jul 1, 2025–Jul 1, 2025, discovered Jul 1, 2025 — the first regulatory filing landed 62 days later (flagged late). 257,481 individuals reported across the linked filings. Data reported: Health (basic), Identity (basic), and PHI. Notifications rolled out on a 53-day schedule across 8 filings beginning Sep 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

62days

Discovered → first regulatory filing

Discovery variance

71days

Range of discovered_at dates across filings

Filing span

53days

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 clocksOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 71dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedTexas✓ TX CRA notice dueFull 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.