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

Confirmed12 filings · 8 statesUnverified claimConfirmedEnforcedcritical sensitivity

Merged incident · 12 filings

Xsolis — January 2026 breach

Clustered 12 filings across 8 jurisdictions · filing window Jun 5, 2026 → Jul 28, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

Affected · reported

2,523,302

First → last filing

Jun 5, 2026 → Jul 28, 2026

Merge confidence

100%

incident inc_9c6b90aedb164215 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Jan 20, 2026–Jan 22, 2026, discovered Jan 22, 2026 — the first regulatory filing landed 134 days later (flagged late). 2,523,302 individuals reported across the linked filings. Data reported: Government ID, Minor, Health (basic), and 2 more. Notifications rolled out on a 53-day schedule across 12 filings beginning Jun 5, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

134days

Discovered → first regulatory filing

Discovery variance

0days

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 clocksWashington✗ WA AG >90dTexas✗ TX AG >30dMassachusetts✗ MA AG >90dHIPAA✓ HHS notifiedFull 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.