Clustered 3 filings across 3 jurisdictions · filed Jul 28, 2025. View entity profile → Other incidents for this victim →
incident inc_8830c32776f34237 · merge_method human · 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.
Health (basic) · Identity (basic) · Financial account
ME RI VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 8, 2024 → Sep 6, 2024
When the intrusion reportedly occurred, per the linked filings
May 29, 2025
Reported by VERMONT AG, HHS OCR, MAINE AG filings
Wood River Health notified consumers of a data security incident affecting an employee email account between August 8, 2024, and September 6, 2024. The unauthorized actor accessed the account, potentially viewing names, SSNs, medical records, and login credentials. WRH engaged outside investigators, notified federal law enforcement, and offered credit monitoring services.
Wood River Health (RI) reported to HHS on 2025-07-28 a Hacking/IT Incident (email phishing) affecting 54,926 individuals. An employee was targeted by an email phishing scheme exposing PHI including clinical, demographic, and financial information. The CE notified HHS, affected individuals, and the media, provided substitute notice, and offered complimentary credit monitoring. Additional administrative, technical, and security safeguards were implemented. Breached information located on Email.
Affected (this filing): 54,926
Wood River Health, a healthcare organization, reported an external system breach that was discovered on May 29, 2025. The breach, which occurred on August 8, 2024, affected 64 Maine residents. The company notified the affected individuals in writing on July 28, 2025, and offered 12 months of identity theft protection services through TransUnion.
Affected (this filing): 64
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.