Colorado Farm Bureau Insurance Company reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-28. The breach occurred from 12/4/2020 to 1/7/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Apr 28, 2021 → May 3, 2021. View entity profile → Other incidents for this victim →
incident inc_0a5e59eb39284bdd · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 4, 2020
When the intrusion reportedly occurred, per the linked filings
Jan 6, 2021
Reported by NEW HAMPSHIRE AG filing
Colorado Farm Bureau Insurance Company reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-28. The breach occurred from 12/4/2020 to 1/7/2021. 1 Montana residents were affected.
Affected (this filing): 1
Colorado Farm Bureau Insurance Company (CFBIC) notified the New Hampshire Attorney General of a phishing incident affecting one NH resident. On or about Jan 6, 2021, CFBIC learned two email accounts were compromised via a phishing campaign. Unauthorized actors accessed account contents between Dec 3, 2020, and Jan 7, 2021. Affected data included names and Social Security numbers. CFBIC secured accounts, engaged forensic investigators, and offered 24 months of credit monitoring through Kroll.
Affected (this filing): 1
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.