The Affiliated Group reported a data breach to the Montana Attorney General. The breach was reported on 2018-09-18. The breach occurred on 5/16/2018. 21 Montana residents were affected.
Affected (this filing): 21
Clustered 2 filings across 2 jurisdictions · filing window Sep 18, 2018 → Sep 19, 2018. View entity profile → Other incidents for this victim →
incident inc_c866c3ff436747f8 · 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
Mar 28, 2018
Reported by CALIFORNIA AG filing
May 16, 2018
When the intrusion reportedly occurred, per the linked filings
The Affiliated Group reported a data breach to the Montana Attorney General. The breach was reported on 2018-09-18. The breach occurred on 5/16/2018. 21 Montana residents were affected.
Affected (this filing): 21
The Affiliated Group (TAG) reported a data breach affecting 1,289 California residents. On or about November 20, 2017, an employee's email account was compromised via phishing, allowing an unauthorized actor to send phishing emails and access the account. The investigation determined that names, Social Security numbers, medical record numbers, limited treatment information, subscriber IDs, and financial account numbers were potentially accessible. TAG disabled the account, reset passwords, engaged forensic investigators, and provided 12 months of credit monitoring through TransUnion.
Affected (this filing): 1,289
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.