Maxim Healthcare Group reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-04. The breach occurred from 10/30/2020 to 12/4/2020. 5 Montana residents were affected.
Affected (this filing): 5
Clustered 2 filings across 2 jurisdictions · filed Nov 4, 2021. View entity profile → Other incidents for this victim →
incident inc_ae410689d7374c75 · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 30, 2020
When the intrusion reportedly occurred, per the linked filings
Dec 4, 2020
Reported by CALIFORNIA AG filing
Maxim Healthcare Group reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-04. The breach occurred from 10/30/2020 to 12/4/2020. 5 Montana residents were affected.
Affected (this filing): 5
Maxim Healthcare Group experienced unauthorized access to employee email accounts between October 1, 2020, and December 4, 2020. The incident involved the compromise of valid credentials, leading to the collection of email data. The breach potentially exposed personal information, including names, addresses, and government identifiers, affecting 88 Rhode Island residents. Maxim implemented MFA, engaged a new Security Operations Center, and offered 12 months of credit monitoring.
Affected (this filing): 88
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.