Cardiology Associates of Fredericksburg, Ltd. reported a data breach to the Montana Attorney General. The breach was reported on 2025-06-20. The breach occurred on 02/17/2025. 5 Montana residents were affected.
Affected (this filing): 5
Clustered 2 filings across 2 jurisdictions · filing window Jun 20, 2025 → Jun 26, 2025. View entity profile → Other incidents for this victim →
incident inc_5c5b4433a1984a5f · 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 17, 2025
When the intrusion reportedly occurred, per the linked filings
Feb 17, 2025
Reported by NEW HAMPSHIRE AG filing
Cardiology Associates of Fredericksburg, Ltd. reported a data breach to the Montana Attorney General. The breach was reported on 2025-06-20. The breach occurred on 02/17/2025. 5 Montana residents were affected.
Affected (this filing): 5
Cardiology Associates of Fredericksburg, Ltd. notified the New Hampshire Attorney General of a cybersecurity event discovered on February 17, 2025. Unauthorized access resulted in the acquisition of patient data, including names, addresses, SSNs, and medical information. 26 New Hampshire residents were affected. The organization engaged forensic investigators, reset passwords, and offered 24 months of credit monitoring.
Affected (this filing): 26
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.