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

Modoc Medical Center — January 2026 breach

Clustered 5 records across 3 jurisdictions: 4 filings and 1 leak-site claim · filing window Mar 27, 2026 → Sep 22, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

3

Affected · reported

29,688

First → last dated filing

Mar 27, 2026 → Sep 22, 2026

Merge confidence

100%

incident inc_8e093effee16410a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 19, 2026–Jan 27, 2026, discovered Jan 27, 2026 — the first regulatory filing landed 59 days later. 29,688 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 179-day schedule across 3 dated filings beginning Mar 27, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
59days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
39days 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
179days

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

Jan 19, 2026breach begins
Jan 27, 2026discovered
notification delay · 59 days
Mar 27, 2026first dated filing
Sep 22, 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. FEB 16Leak siteworldleaks postfirst record · attacker claim · unverifiedday 0
  2. MAR 27HHS OCRHHS OCR noticestates nationwide total 29,688+38d
  3. SEP 1MA AGMA AG noticefiling day not on record · 10 MA residents—
  4. SEP 22NH AGNH AG notice4 NH residents+217d
  5. SEP 22CA AGCA AG noticemost recent · no count stated+217d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 19, 2026 – Jan 27, 2026
MA AG
Discovered
Jan 27, 2026· 8d undetected
MA AG + NH AG + CA AG
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MA AG + NH AG +1
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)

29,688

Sum of filed state slices

14· 0.0% of stated

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

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

179 days

Cadence

~1 / 89.5d

vs. multi-state median

29.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.