DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed7 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedworldleakshigh sensitivity
Merged incident · 7 records

Lake Region Healthcare — May 2025 breach

Clustered 7 records across 6 jurisdictions: 6 filings and 1 leak-site claim · filing window Jul 1, 2026 → Jul 7, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 records

States

6

Affected · reported

167,617

First → last dated filing

Jul 1, 2026 → Jul 7, 2026

Merge confidence

100%

incident inc_d1d9939d4df74964 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 19, 2025, discovered May 19, 2025 — the first regulatory filing landed 408 days later. 167,617 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 1 more. Notifications rolled out on a 6-day schedule across 5 dated filings beginning Jul 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
408days

Discovered → first regulatory filing

Discovery variance
382days

Range of discovered_at dates across filings

Leak precedence
384days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
6days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 19, 2025breach begins
May 19, 2025discovered · members disagree
notification delay · 408 days
Jul 1, 2026first dated filing
Jul 7, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. MAY 16Leak siteworldleaks postfirst record · attacker claim · unverifiedday 0
  2. JUL 1HHS OCRHHS OCR noticestates nationwide total 167,617+411d
  3. JUL 1IN AGIN AG noticestates nationwide total 167,617+411d
  4. JUL 1MA AGMA AG notice20 MA residents+411d
  5. JUL 1NE AGNE AG noticefiling day not on record · no count stated—
  6. JUL 3TX AGTX AG noticestates nationwide total 167,617+413d
  7. JUL 7NH AGNH AG noticemost recent · 6 NH residents+417d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 19, 2025
IN AG
Discovered
May 19, 2025NH AGJun 5, 2026TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + MA AG + TX AG +2
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)

167,617

Sum of filed state slices

372· 0.2% of stated

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

US167,617
TX294
IN52
MA20
NH6

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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing6 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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

6 days

Cadence

~1 / 1.5d

vs. multi-state median

1.0× faster

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.