DisclosureLens
Leak SiteHHS OCRState AGConfirmed12 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmedusamoderate sensitivity
Merged incident · 12 filings

Insightin Health — September 2025 breach

Clustered 12 filings across 8 jurisdictions · filing window Sep 23, 2025 Apr 1, 2026. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

12 filings

States

7

Affected · reported

1,949,534

First → last filing

Sep 23, 2025 Apr 1, 2026

Merge confidence

100%

incident inc_6bffa5a1b1f14bef · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Sep 17, 2025–Sep 23, 2025, discovered Sep 1, 2025 — the first regulatory filing landed 137 days later (flagged late). 1,949,534 individuals reported across the linked filings. Data reported: PHI, Health (basic), Identity (basic), and 1 more. Notifications rolled out on a 190-day schedule across 10 filings beginning Sep 23, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
137days

Discovered → first regulatory filing

Discovery variance
127days

Range of discovered_at dates across filings

Leak precedence
115days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
190days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksVermont VT AG >45 bdayOregon OR AG >45dCalifornia CA 60-day late · 162dWashington WA AG >90dTexas TX AG >30dLeak gap Leak >90dFull clock table in Litigation Timeline

Incident timeline

Sep 17, 2025breach begins
Sep 1, 2025discovered · members disagree
notification delay · 137 days
Jan 16, 2026first filing
Apr 1, 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. SEP 23Leak sitemedusa postfirst filing · attacker claim · unverifiedday 0
  2. SEP 26Leak sitemedusa postattacker claim · unverified+4d
  3. JAN 16HHS OCRHHS OCR noticestates nationwide total 1,949,534+115d
  4. JAN 28VT AGVT AG noticeno count stated+127d
  5. MAR 4MT AGMT AG notice139 MT residents+162d
  6. MAR 4VT AGVT AG noticeno count stated+162d
  7. MAR 5OR AGOR AG noticestates nationwide total 1,144,686+163d
  8. MAR 5CA AGCA AG noticeno count stated+163d
  9. MAR 5WA AGWA AG notice11,740 WA residents+163d
  10. MAR 10TX AGTX AG noticestates nationwide total 1,777,141+168d
  11. APR 1VT AGVT AG notice11,496 VT residents+190d
  12. APR 1CA AGCA AG noticemost recent · no count stated+190d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 17, 2025Sep 23, 2025
VT AG
Discovered
Sep 1, 2025VT AG + CA AGSep 23, 2025MT AG + VT AG + OR AG +2Jan 6, 2026TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · PHI · PII
HHS OCR + CA AG + WA AG +3
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)

1,949,534

Sum of filed state slices

166,721· 8.6% of stated

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

US1,949,534
TX143,346
WA11,740
VT11,496
MT139

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 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
Reviewed
operator-reviewed Aug 9, 2026 · at least one link edge was human-adjudicated
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

190 days

Cadence

~1 / 17.3d

vs. multi-state median

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