Meridian Behavioral Healthcare, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-12-22. The breach occurred on 8/11/2023. 10 Montana residents were affected.
Affected (this filing): 10
Clustered 2 filings across 2 jurisdictions · filed Dec 22, 2023. View entity profile → Other incidents for this victim →
incident inc_f35881ff68e84686 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 11, 2023
When the intrusion reportedly occurred, per the linked filings
Aug 11, 2023
Reported by NEW HAMPSHIRE AG filing
Meridian Behavioral Healthcare, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-12-22. The breach occurred on 8/11/2023. 10 Montana residents were affected.
Affected (this filing): 10
Meridian Behavioral Healthcare, Inc. notified the NH AG on Dec 22, 2023, of a breach discovered Aug 11, 2023. Unauthorized access impacted PHI and PII of 15 NH residents. Meridian secured the network, reset passwords, and engaged forensic investigators. No evidence of misuse was found. Credit monitoring offered.
Affected (this filing): 15
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.