DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedembargohigh sensitivity
Merged incident · 9 filings

Weiser Memorial Hospital — September 2024 breach

Clustered 9 filings across 8 jurisdictions · filing window Sep 4, 2024 → May 15, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

34,249

First → last filing

Sep 4, 2024 → May 15, 2025

Merge confidence

100%

incident inc_6704a0e3cdc448cc · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Sep 4, 2024–Sep 4, 2025, discovered Sep 4, 2024 — the first regulatory filing landed 250 days later (flagged late). 34,249 individuals reported across the linked filings. Data reported: Government ID, PII, PHI, and 2 more. Notifications rolled out on a 253-day schedule across 7 filings beginning Sep 4, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
250days

Discovered → first regulatory filing

Discovery variance
229days

Range of discovered_at dates across filings

Leak precedence
250days 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
253days

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 >180dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 4, 2024breach begins
Sep 4, 2024discovered · members disagree
notification delay · 250 days
May 12, 2025first filing
May 15, 2025most 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 4Leak siteembargo postfirst filing · attacker claim · unverifiedday 0
  2. SEP 9Leak siteembargo postattacker claim · unverified+5d
  3. MAY 12MT AGMT AG notice251 MT residents+250d
  4. MAY 12IN AGIN AG noticestates nationwide total 34,249+250d
  5. MAY 12VT AGVT AG noticeno count stated+250d
  6. MAY 13OR AGOR AG noticestates nationwide total 34,249+251d
  7. MAY 13ME AGME AG noticestates nationwide total 34,249+251d
  8. MAY 13WA AGWA AG notice1,163 WA residents+251d
  9. MAY 15CA AGCA AG noticemost recent · no count stated+253d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 4, 2024
MT AG
Discovered
Sep 4, 2024MT AG + VT AG + WA AGApr 21, 2025OR AG + ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + VT AG + ME AG +2
Attack vector
Unauthorized Access
MT AG

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)

34,249

Sum of filed state slices

1,464· 4.3% of stated

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

US34,249
WA1,163
MT251
IN36
ME14

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 filing7 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 23, 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

253 days

Cadence

~1 / 31.6d

vs. multi-state median

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