Clustered 4 filings across 3 jurisdictions · filing window Nov 5, 2024 → Dec 30, 2024. View entity profile → Other incidents for this victim →
incident inc_a4604a5ef1194952 · merge_method deterministic · confidence 100%
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.
IN MI MT
HHS OCR · State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
May 28, 2024
When the intrusion reportedly occurred, per the linked filings
Michigan Masonic Home reported a data breach to the Montana Attorney General. The breach was reported on 2024-11-05. The breach occurred from 5/28/2024 to 7/18/2024. 2 Montana residents were affected.
Affected (this filing): 2
Michigan Masonic Home reported a data breach to the Indiana Attorney General. The breach occurred on 2024-05-28 and was reported on 2024-11-05. 1 Indiana residents were affected. 4,189 individuals affected in total.
Affected (this filing): 4,189
Michigan Masonic Home reported to HHS on 2024-11-08 a Hacking/IT Incident affecting 3255 individuals. Breached information located on Email. Employees were targeted by an email phishing scheme compromising PHI including names, addresses, DOB, SSN, driver's license, financial info, diagnoses, lab results, and medications. The entity provided credit monitoring and implemented safeguards.
Affected (this filing): 3,255
Michigan Masonic Home reported a data breach to the Indiana Attorney General. The breach occurred on 2024-07-30 and was reported on 2024-12-30. 2 Indiana residents were affected. 3,277 individuals affected in total.
Affected (this filing): 3,277
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.