GEICO Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2023-05-27 and was reported on 2024-01-29. 2,327 Indiana residents were affected. 71,490 individuals affected in total.
Affected (this filing): 71,490
Clustered 2 filings across 2 jurisdictions · filing window Jan 29, 2024 → Jan 31, 2024. View entity profile → Other incidents for this victim →
incident inc_d9a1377b8f794591 · 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.
Government ID
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 27, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 6, 2023
Reported by MAINE AG filing
GEICO Corporation reported a data breach to the Indiana Attorney General. The breach occurred on 2023-05-27 and was reported on 2024-01-29. 2,327 Indiana residents were affected. 71,490 individuals affected in total.
Affected (this filing): 71,490
GEICO Corporation reported that its employees were affected by a third-party data breach involving the MOVEit file transfer tool vulnerability. The breach occurred at Delta Dental of California (DDC), which provides dental insurance to GEICO employees. Between May 27, 2023, and May 30, 2023, unauthorized actors exploited the vulnerability and accessed files from DDC's MOVEit server. The breach was discovered by DDC on July 6, 2023. The compromised information included names and driver's license numbers. Affected individuals were offered 24 months of free identity monitoring services.
Affected (this filing): 34
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.