Ciox Health LLC, d/b/a Datavant Group reported a data breach to the Montana Attorney General. The breach was reported on 2025-02-11. The breach occurred from 05/08/2024 to 05/09/2024. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filed Feb 11, 2025. View entity profile → Other incidents for this victim →
incident inc_97bf032b623c4ea0 · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 8, 2024
When the intrusion reportedly occurred, per the linked filings
May 9, 2024
Reported by MAINE AG filing
Ciox Health LLC, d/b/a Datavant Group reported a data breach to the Montana Attorney General. The breach was reported on 2025-02-11. The breach occurred from 05/08/2024 to 05/09/2024. 3 Montana residents were affected.
Affected (this filing): 3
Ciox Health LLC (d/b/a Datavant Group), a healthcare data technology company, reported a May 2024 phishing email attack in which an unauthorized party gained access to a single employee mailbox between May 8–9, 2024. Data potentially affected included names, addresses, SSNs, financial account information, driver's licenses, passports, health information, and employee credentials. 17 Maine residents were affected out of 49,454 total. Kroll 24-month identity monitoring was offered.
Affected (this filing): 17
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.