Confirmed breach. Intrusion Mar 13, 2025–Mar 16, 2025, discovered Mar 16, 2025 — the first regulatory filing landed 36 days later. 6 individuals reported across the linked filings.
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.
Regulatory clocksVermont⏱ VT AG >14 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
6
Data types
—
Jurisdictions
2
MT VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 13, 2025 → Mar 16, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Mar 16, 2025
Reported by VERMONT AG filing
36 days
🍁Vermont State AGFirst filinglinked via multistate filing link · 100%
Horizon Behavioral Health disclosed a ransomware incident discovered on March 16, 2025, with activity starting around March 13, 2025. The breach impacted patient demographic data (SSN, DL), clinical information, and insurance claims. Horizon engaged forensic experts, notified the FBI and CISA, and provided complimentary identity monitoring to affected individuals.
Horizon Behavioral Health reported a data breach to the Montana Attorney General. The breach was reported on 2025-04-21. The breach occurred from 3/13/2025 to 3/16/2025. 6 Montana residents were affected.
Affected (this filing): 6
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.