Drug Free Workplaces USA reported a data breach to the Montana Attorney General. The breach was reported on 2023-10-26. The breach occurred from 3/29/2023 to 5/4/2023. 23 Montana residents were affected.
Affected (this filing): 23
Clustered 2 filings across 2 jurisdictions · filing window Oct 26, 2023 → Oct 27, 2023. View entity profile → Other incidents for this victim →
incident inc_8570208bf2d844d9 · merge_method human · 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
Mar 29, 2023
When the intrusion reportedly occurred, per the linked filings
Sep 29, 2023
Reported by MAINE AG filing
Drug Free Workplaces USA reported a data breach to the Montana Attorney General. The breach was reported on 2023-10-26. The breach occurred from 3/29/2023 to 5/4/2023. 23 Montana residents were affected.
Affected (this filing): 23
Drug Free Workplaces USA, LLC, a healthcare organization, reported an external system breach that occurred between March 29, 2023, and May 4, 2023. The breach, discovered on September 29, 2023, resulted in the acquisition of names and Social Security numbers. A total of 37,705 individuals were affected, including 21 Maine residents. The company provided written notification to affected consumers on October 27, 2023, and offered identity theft protection services.
Affected (this filing): 37,705
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.