All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed5 filings · 4 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 5 filings

Michigan Masonic Home — May 2024 breach

Clustered 5 filings across 4 jurisdictions · filing window Nov 5, 2024 → Dec 30, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

4,189

First → last dated filing

Nov 5, 2024 → Dec 30, 2024

Merge confidence

100%

incident inc_a4604a5ef1194952 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. Intrusion May 28, 2024–Jul 18, 2024, discovered May 28, 2024. 4,189 individuals reported across the linked filings. Data reported: Government ID, Health (basic), PII, and 3 more. Notifications rolled out on a 55-day schedule across 4 dated filings beginning Nov 5, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span

55days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 28, 2024breach begins

May 28, 2024discovered

Nov 5, 2024first dated filing

Dec 30, 2024most 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 about this breach

NOV 1IL AGIL AG noticefiling day not on record · no count statedauto-linked—
NOV 5MT AGMT AG noticefirst filing · 2 MT residentsauto-linkedday 0
NOV 5IN AGIN AG noticestates nationwide total 4,189auto-linkedday 0
NOV 8HHS OCRHHS OCR noticestates nationwide total 3,255auto-linked+3d
DEC 30IN AGIN AG noticemost recent · states nationwide total 3,277+55d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: May 28, 2024 – Jul 18, 2024
Discovered: May 28, 2024
Data types: Financial · Health (basic) · Identity (basic) · Government ID · PHI · PII
Attack vector: Phishing

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)

4,189

Sum of filed state slices

4· 0.1% 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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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

55 days

Cadence

~1 / 18.3d

vs. multi-state median

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