Clustered 4 filings across 3 jurisdictions · filed Mar 31, 2025. View entity profile → Other incidents for this victim →
incident inc_23dedf6bca5543de · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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 OR VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 29, 2024
When the intrusion reportedly occurred, per the linked filings
Sep 12, 2024
Reported by VERMONT AG filing
Willamette Family Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-05-29 and was reported on 2025-03-31. 1 Indiana residents were affected. 4,327 individuals affected in total.
Affected (this filing): 4,327
Willamette Family, Inc. notified consumers of a cybersecurity incident affecting email accounts. Unauthorized access may have originated on May 29, 2024, and was discovered on September 12, 2024. Impacted data included names and Doctor/Provider names. The company engaged forensic investigators, reset credentials, and expanded MFA usage.
Willamette Family, Inc. reported to HHS on 2025-03-31 a Hacking/IT Incident affecting 3899 individuals. Breached information located on Email.
Affected (this filing): 3,899
Willamette Family, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2025-03-31. The breach occurred during 5/29/2024 - 9/29/2024. The breach was discovered on 9/12/20249/27/2024. 4,327 individuals were affected. Notice was sent on 3/31/2025.
Affected (this filing): 4,327
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.