Cache Valley Ear Nose & Throat reported a data breach to the Montana Attorney General. The breach was reported on 2025-11-21. The breach occurred on 02/04/2025. 16 Montana residents were affected.
Affected (this filing): 16
Clustered 2 filings across 2 jurisdictions · filed Nov 21, 2025. View entity profile → Other incidents for this victim →
incident inc_96588de7015d4924 · 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
Feb 4, 2025
When the intrusion reportedly occurred, per the linked filings
Feb 4, 2025
Reported by NEW HAMPSHIRE AG filing
Cache Valley Ear Nose & Throat reported a data breach to the Montana Attorney General. The breach was reported on 2025-11-21. The breach occurred on 02/04/2025. 16 Montana residents were affected.
Affected (this filing): 16
Cache Valley Ear Nose & Throat (CVENT) notified the New Hampshire Attorney General of a cybersecurity event occurring on February 4, 2025. The incident involved unauthorized access to email systems, likely via phishing, resulting in the viewing and copying of patient information including names, addresses, provider details, and insurance information. One New Hampshire resident was affected. CVENT offered credit monitoring services and notified the regulator on November 21, 2025.
Affected (this filing): 1
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.