DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed11 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmontihigh sensitivity
Merged incident · 11 filings

Wayne Memorial Hospital — May 2024 breach

Clustered 11 filings across 10 jurisdictions · filing window Jun 3, 2024 → Sep 9, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

163,440

First → last filing

Jun 3, 2024 → Sep 9, 2025

Merge confidence

100%

incident inc_6b1d7e0ece094bfe · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 2 unverified claims. Intrusion May 30, 2024–Jun 3, 2024, discovered Jun 3, 2024 — the first regulatory filing landed 60 days later (flagged late). 163,440 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 6 more. Notifications rolled out on a 463-day schedule across 9 filings beginning Jun 3, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
60days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
60days 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
463days

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 >180dMaine✗ ME AG >90d · 461dVermont✗ VT AG >45 bdayTexas✗ TX AG >30dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

May 30, 2024breach begins
Jun 3, 2024discovered
notification delay · 60 days
Aug 2, 2024first filing
Sep 9, 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. JUN 3Leak sitemonti postfirst filing · attacker claim · unverifiedday 0
  2. JUN 30Leak sitemonti postattacker claim · unverified+28d
  3. AUG 2HHS OCRHHS OCR noticestates nationwide total 2,500+60d
  4. AUG 2IN AGIN AG noticestates nationwide total 163,440+425d
  5. AUG 27NE AGNE AG notice13 NE residents+450d
  6. SEP 7MA AGMA AG notice50 MA residents+461d
  7. SEP 7ME AGME AG noticestates nationwide total 163,440+461d
  8. SEP 7VT AGVT AG noticeno count stated+461d
  9. SEP 7MT AGMT AG notice5 MT residents+461d
  10. SEP 8NH AGNH AG notice11 NH residents+462d
  11. SEP 9TX AGTX AG noticemost recent · states nationwide total 163,440+463d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2024
IN AG
Discovered
Jun 3, 2024· 4d undetected
NE AG + ME AG + VT AG +3
Data types
Credentials · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
HHS OCR + ME AG + TX AG +5
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)

163,440

Sum of filed state slices

592· 0.4% of stated

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

US163,440
TX373
IN106
MA50
ME34
NE13
NH11
MT5

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

463 days

Cadence

~1 / 46.3d

vs. multi-state median

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