GLOBALClaimed by Hunters InternationalFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Dec 8, 2023bd_c21c41b148e94803
Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
Clustered 5 filings across 4 jurisdictions · filing window Dec 8, 2023 → May 30, 2025. View entity profile → Other incidents for this victim →
incident inc_914c1ec918ab4f45 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
AL MT VT
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 8, 2023
When the intrusion reportedly occurred, per the linked filings
Dec 8, 2023
Reported by VERMONT AG filing
Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
Bradford Health Services, LLC reported to HHS on 2024-02-06 a Hacking/IT Incident affecting 28543 individuals. Breached information located on Network Server.
Bradford Health Services notified Vermont consumers of a data breach detected on December 8, 2023. An unknown actor gained unauthorized access to the network, acquiring files containing personal and protected health information. The company engaged forensic investigators, reported the incident to law enforcement, and is offering identity protection services. The investigation determined specific individuals were impacted by May 15, 2025.
Bradford Health Services reported a data breach to the Montana Attorney General. The breach was reported on 2025-05-30. The breach occurred on 12/08/2023. 44 Montana residents were affected.
Affected (this filing):
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.
Affected (this filing): 28,543