Clustered 2 filings across 2 jurisdictions · filing window Apr 13, 2021 → Apr 15, 2021. View entity profile → Other incidents for this victim →
incident inc_acb4108a5b514368 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
CA ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 23, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 1, 2021
Reported by MAINE AG, CALIFORNIA AG filings
Government Employees Insurance Company reported an external system breach that occurred on January 23, 2021, and was discovered on March 1, 2021. The breach affected 131,913 individuals, compromising names and driver's license or non-driver ID card numbers. Affected individuals were notified in writing on April 9, 2021, and offered 12 months of identity protection services.
Affected (this filing): 131,913
Government Employees Insurance Company (GEICO) reported a data breach occurring between January 21, 2021, and March 1, 2021. Fraudsters used information acquired elsewhere to gain unauthorized access to victims' driver's license numbers through GEICO's online sales system. The data obtained was limited to driver's license numbers, which could be used to fraudulently apply for unemployment benefits. GEICO secured the website, identified the root cause, and offered one year of IdentityForce identity-theft protection to affected individuals.
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.