DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed12 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified 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

8

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

Sensitive data

identity_governmentminor

Incident timeline

Jan 20, 2026breach begins
Jan 22, 2026discovered
notification delay · 134 days
Jun 5, 2026first filing
Jul 28, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUN 5HHS OCRHHS OCR noticefirst filing · states nationwide total 1,396,519day 0
  2. JUN 5NE AGNE AG noticeno count statedday 0
  3. JUN 5NE AGNE AG noticeno count statedday 0
  4. JUN 5IN AGIN AG noticestates nationwide total 1,396,519day 0
  5. JUN 19CA AGCA AG noticeno count stated+14d
  6. JUN 19WA AGWA AG notice24,711 WA residents+14d
  7. JUN 22TX AGTX AG noticestates nationwide total 1,396,519+17d
  8. JUN 25NH AGNH AG notice47 NH residents+20d
  9. JUN 30MA AGMA AG noticeno count stated+25d
  10. JUL 21CA AGCA AG noticeno count stated+46d
  11. JUL 23TX AGTX AG noticestates nationwide total 2,523,302+48d
  12. JUL 28NH AGNH AG noticemost recent · 220 NH residents+53d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 20, 2026
IN AG
Discovered
Jan 22, 2026· 2d undetected
NE AG + CA AG + WA AG +3
Data types
Health (basic) · Identity (basic) · Government ID · Minor · PHI
HHS OCR + NE AG + CA AG +4
Attack vector
Unauthorized Access
HHS OCR

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)

2,523,302

Sum of filed state slices

164,509· 6.5% of stated

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

US2,523,302
TX139,424
WA24,711
NH220
IN154

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 filing12 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
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

53 days

Cadence

~1 / 4.8d

vs. multi-state median

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