Resource Center — February 2026 breach

Clustered 4 filings across 3 jurisdictions · filing window Jul 1, 2026 → Jul 17, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

12,490

First → last filing

Jul 1, 2026 → Jul 17, 2026

Merge confidence

100%

incident inc_20845cc269dd405b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Feb 4, 2026–Feb 12, 2026, discovered Feb 12, 2026 — the first regulatory filing landed 139 days later. 12,490 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 2 more. Notifications rolled out on a 16-day schedule across 4 filings beginning Jul 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

139days

Discovered → first regulatory filing

Discovery variance

140days

Range of discovered_at dates across filings

Filing span

16days

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 clocksHIPAA✓ HHS notifiedTexas✓ TX AG ≤30dFull 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.