Confirmed breach. Intrusion Nov 14, 2022–Dec 4, 2022, discovered Dec 4, 2022 — the first regulatory filing landed 54 days later. 53,668 individuals reported across the linked filings.
Howard Memorial Hospital notified consumers of a data breach where files were stolen between Nov 14 and Dec 4, 2022. Impacted data included names, SSNs, DOBs, and PHI. The hospital engaged Cyberscout for forensics, secured its network, and offered 12 months of credit monitoring. No specific count of affected individuals was disclosed.
VT AG >14 bday
🦬Montana State AGlinked via same-victim cross-source · 100%
Howard Memorial Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2023-01-27. The breach occurred from 11/14/2022 to 12/4/2022. 7 Montana residents were affected.
Affected (this filing): 7
🇺🇸ARHHS OCRlinked via same-victim cross-source · 100%
Howard Memorial Hospital reported to HHS on 2023-01-27 a Hacking/IT Incident affecting 53,668 individuals. Breached information located on Network Server. The cyber-attack exposed PHI including names, DOB, addresses, SSNs, diagnoses, lab results, and medications. The entity notified HHS, individuals, and media, and strengthened administrative and technical safeguards.
Affected (this filing): 53,668
🦞Maine State AGMost recentlinked via multistate filing link · 100%
Howard Memorial Hospital reported a data breach to the Maine Attorney General, indicating an external system breach (hacking) occurred on November 14, 2022. The incident was discovered on January 13, 2023, and affected 2 Maine residents. The compromised data included names and Social Security Numbers. The hospital offered 12 months of identity protection and credit monitoring services to those affected.
Affected (this filing): 2
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.