Blue Cross and Blue Shield of Kansas City reported a data breach to the Montana Attorney General. The breach was reported on 2021-05-26. The breach occurred on 2/23/2021. 4 Montana residents were affected.
Affected (this filing): 4
Clustered 2 filings across 2 jurisdictions · filing window May 26, 2021 → Jun 2, 2021. View entity profile → Other incidents for this victim →
incident inc_d8a60aedcdfe45ea · 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
Feb 23, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 27, 2021
Reported by MAINE AG filing
Blue Cross and Blue Shield of Kansas City reported a data breach to the Montana Attorney General. The breach was reported on 2021-05-26. The breach occurred on 2/23/2021. 4 Montana residents were affected.
Affected (this filing): 4
Blue Cross and Blue Shield of Kansas City reported a data breach affecting 47,034 individuals, including 164 Maine residents. The breach occurred on February 23, 2021, and was discovered on March 27, 2021. Described as an external system breach or hacking, it resulted in the compromise of names and Social Security Numbers. The company began notifying affected individuals in writing on May 26, 2021, and offered 24 months of identity theft protection services.
Affected (this filing): 47,034
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.