Clustered 3 filings across 3 jurisdictions · filing window Dec 6, 2022 → Dec 7, 2022. View entity profile → Other incidents for this victim →
incident inc_0fc61a6c686d4b16 · 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.
Identity (basic) · Government ID · Health (basic)
MD MT NH
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 7, 2022
When the intrusion reportedly occurred, per the linked filings
Feb 7, 2022
Reported by NEW HAMPSHIRE AG filing
Blakehurst reported a data breach to the Montana Attorney General. The breach was reported on 2022-12-06. The breach occurred on 2/7/2022. 1 Montana residents were affected.
Affected (this filing): 1
Blakehurst (MD) reported to HHS OCR on 2022-12-06 a Hacking/IT Incident affecting 1,047 individuals via an email phishing scheme targeting multiple employees. PHI involved included names, Social Security numbers, addresses, drivers' license numbers, dates of birth, diagnoses, and claims and financial information. Breached information was located on Email systems. The CE notified HHS, affected individuals, and media, provided credit monitoring, and implemented additional safeguards including staff email security training.
Affected (this filing): 1,047
Blakehurst, a senior living community, notified the NH AG of a data security incident discovered on Feb 7, 2022. Unauthorized access to employee email accounts occurred, potentially exposing PII, SSNs, financial data, and PHI of residents. Notices were mailed on Dec 6, 2022. No evidence of misuse was found.
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.