Clustered 3 filings across 2 jurisdictions · filing window Sep 16, 2022 → Sep 20, 2022. View entity profile → Other incidents for this victim →
incident inc_6311fc4dbb434b8f · merge_method deterministic · confidence 100%
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.
MT NH
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 12, 2021
When the intrusion reportedly occurred, per the linked filings
Easterseals-Goodwill Northern Rocky Mountain reported a data breach to the Montana Attorney General. The breach was reported on 2022-09-16. The breach occurred from 10/12/2021 to 11/11/2021. 7,552 Montana residents were affected.
Affected (this filing): 7,552
EasterSeals-Goodwill of the Northern Rocky Mountains reported to HHS on 2022-09-16 a Hacking/IT Incident affecting 3,886 individuals. Breached information located on Email. Employees were victims of an email phishing attack exposing PHI including names, SSNs, addresses, driver's license numbers, DOB, medications, diagnoses, and financial/claims data. CE provided credit monitoring and implemented safeguards.
Affected (this filing): 3,886
State of New Hampshire Attorney General breach notification filed by Easterseals-Goodwill Northern Rocky Mountain on September 20, 2022. The attached consumer notification letter is empty (pages 1-9 contain no text). No specific breach details, dates, data types, or response actions are provided in the filing.
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.