Clustered 3 filings across 3 jurisdictions · filing window Dec 24, 2023 → Aug 2, 2024. View entity profile → Other incidents for this victim →
incident inc_33f103b7b19744ba · merge_method deterministic · confidence 100%
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Identity (basic) · Government ID · Health (basic)
NY VT
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
The Hamilton-Madison House is a historic 118-year old settlement house/multi service agency addressing the education, health and social needs of immigrant and ethnic minority communities. As you understand there are so many personal files. We will upload about10Gb of their files and you can find so much interesting in there (passports, birth certificates, IDs etc).
Hamilton-Madison House notified consumers of a data breach involving unauthorized access to personal information, including names, SSNs, DOBs, and medical data. The organization is offering 12 months of credit monitoring and identity restoration services via Experian IdentityWorks.
Hamilton-Madison House, Inc. reported to HHS on 2024-08-02 a Hacking/IT Incident affecting 1,114 individuals. Breached information located on Network Server. The incident involved PHI including names, birthdates, addresses, driver's license and SSN numbers, medical record numbers, health insurance information, and medications. The entity notified HHS, affected individuals, and provided media notification, while implementing additional administrative, technical, security, and physical safeguards.
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.
Affected (this filing): 1,114