Clustered 4 filings across 4 jurisdictions · filed Jul 24, 2025. View entity profile → Other incidents for this victim →
incident inc_0fcb67e83a194dce · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
ME MI NH VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 14, 2025 → Apr 15, 2025
When the intrusion reportedly occurred, per the linked filings
Apr 15, 2025
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
Jun 19, 2025
Reported by MAINE AG filing
McKenzie Memorial Hospital notified consumers of a data breach occurring between April 14-15, 2025. Unauthorized access may have resulted in the exposure of names. The hospital engaged third-party investigators, notified law enforcement, and is offering 12 months of credit monitoring. The incident status is contained.
McKenzie Memorial Hospital reported a data breach to the Maine Attorney General, indicating that an external system breach (hacking) occurred on April 14, 2025. The breach was discovered on June 19, 2025, and affected 6 Maine residents. The hospital provided written notification to affected individuals on July 24, 2025, and offered 12 months of credit monitoring and identity theft protection services through TransUnion.
Affected (this filing): 6
McKenzie Memorial Hospital reported to HHS on 2025-07-24 a Hacking/IT Incident affecting 58839 individuals. Breached information located on Network Server.
Affected (this filing): 58,839
McKenzie Memorial Hospital notified the NH AG of a data incident where an unauthorized actor accessed files between April 14-15, 2025. The breach affected 2 NH residents, exposing names, SSNs, and financial account info. The hospital engaged law enforcement and forensic specialists, secured the network, and offered 12 months of credit monitoring.
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.