Clustered 2 filings across 2 jurisdictions · filing window Dec 15, 2023 → Jan 21, 2024. View entity profile → Other incidents for this victim →
incident inc_85734d18da474d8a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Genetic / health-sensitive
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 DE
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 1, 2023 → Sep 1, 2023
When the intrusion reportedly occurred, per the linked filings
Oct 1, 2023
Reported by DELAWARE AG, CALIFORNIA AG filings
23andMe, Inc. notified Delaware residents of a credential stuffing attack occurring between May and September 2023. A threat actor accessed optional DNA Relatives profile data, including ancestry reports, DNA segments, and personal details, which was posted to BreachForums. 23andMe reset passwords, enforced two-factor authentication, paused features, and engaged law enforcement and forensic experts.
23andMe disclosed a credential stuffing attack occurring between late April and September 2023, discovered on October 1, 2023. Threat actors used compromised credentials to access customer accounts, exfiltrating DNA Relatives profile data, genetic health reports, and personal settings. The company engaged forensic experts, notified law enforcement, forced password resets, and mandated two-step verification.
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.