Skip to content
Credential stuffingResolved

23andMe credential-stuffing breach

Attackers used credentials reused from prior breaches to access 23andMe accounts, then leveraged the 'DNA Relatives' feature to scrape ancestry and genetic profile data on 6.9 million users from compromised relatives' connections.

Victim
23andMe Holding Co.
Loss
$50.0M
records
6.9M
users
6.9M

On 6 October 2023, 23andMe β€” the U.S. consumer-genetic-testing company β€” publicly confirmed that attackers had compromised customer accounts via credential stuffing using credentials reused from prior breaches. The directly compromised account count was small (~14,000), but the attackers leveraged 23andMe's DNA Relatives social feature to scrape ancestry and profile data on a much larger population: 6.9 million users, approximately half of 23andMe's total customer base.

The incident became the canonical case for credential-reuse cascades through social-graph features and contributed to 23andMe's eventual March 2025 bankruptcy filing.

What happened

23andMe is a direct-to-consumer genetic-testing service. Users submit a saliva sample, receive ancestry and (historically) health-risk reports, and can opt into a feature called DNA Relatives that connects them with other 23andMe users who share genetic material β€” biological relatives the user may or may not have known about.

The DNA Relatives feature, in its 2023 configuration, allowed users to view substantial profile information for their genetic matches by default: names, profile photos, ancestry composition, ethnicity estimates, and shared geographic information. This was an opt-in feature, but most users had opted in to maximise the genealogy-discovery value.

The attackers' approach:

  1. Credential stuffing: tested credential pairs from prior breaches (LinkedIn 2012, Adobe 2013, others) against 23andMe accounts. Approximately 14,000 accounts were directly compromised over months.
  2. Leveraged DNA Relatives: for each compromised account, scraped profile information for all the account's genetic matches β€” typically dozens to thousands of relatives' profiles per compromised account.
  3. Aggregated: across the 14,000 compromised accounts, profile data on approximately 6.9 million unique 23andMe users was captured β€” roughly half of 23andMe's total customer base.

Crucially, the attackers did not exfiltrate raw genetic sequence data β€” that data is not accessible through the DNA Relatives feature. But the ancestry and ethnicity composition data for each relative was visible, and was captured at scale.

The "Ashkenazi Jewish" sample

On 1 October 2023, a user on a criminal forum using the persona Golem offered a sample dataset of approximately 1 million 23andMe profiles tagged with Ashkenazi Jewish ancestry for sale. The selective ethnic targeting was widely interpreted as deliberate antisemitic targeting. Subsequent listings expanded to additional ethnic populations and finally to the full dataset.

The deliberate ethnic targeting was a distinguishing feature of this breach versus typical data-theft incidents. The attackers' selective release pattern β€” focusing on Ashkenazi Jewish and Chinese-ancestry samples first β€” drew specific media attention and added a discrimination-and-harassment dimension to the harm.

Genetic data scope

Important nuance: raw genetic sequence data was not exfiltrated. The exposed data was:

  • Profile information: names, photos, locations, dates of birth.
  • Ancestry composition: e.g., "32% Northwestern European, 24% Eastern European, 18% Ashkenazi Jewish".
  • Display-name and self-reported ethnicity.
  • Shared family-name suggestions that 23andMe's algorithm provides.

While not raw DNA, the ancestry composition and ethnicity data is genetic-derived and is treated as sensitive personal information under most data-protection frameworks. The exfiltration is therefore a genetic-data breach in regulatory terms, even though the underlying DNA sequences are not in the dataset.

Impact

  • 6.9 million users had profile and ancestry data exposed β€” approximately half of 23andMe's customer base.
  • Direct cost to 23andMe: ~$30M class-action settlement + ~$20M direct remediation + significant customer-loss impact.
  • 23andMe Chapter 11 bankruptcy filing in March 2025 cited the breach and its litigation aftermath among contributing factors, though 23andMe's pre-existing financial pressures were the primary driver.
  • UK ICO and Canadian Privacy Commissioner joint finding in June 2025 that 23andMe's data protection was inadequate, with remediation orders.
  • No specific U.S. enforcement action as of late 2024.

Why it matters

23andMe is the canonical case for credential-stuffing cascades through social-graph features. It established:

  • That credential stuffing remains a primary attack vector despite years of warnings about password reuse. The 14,000 compromised accounts were users whose credentials had appeared in prior breaches and not been rotated.
  • That social-graph features amplify breach impact dramatically. The direct compromise count (14,000) understated the breach scope by a factor of nearly 500x because each compromised account exposed information about hundreds of others.
  • That genetic-derived data β€” even without raw DNA sequences β€” is sensitive personal information requiring elevated protection.
  • That default opt-in to data-sharing features is now treated by regulators as a privacy-design failure. The DNA Relatives default settings β€” which most users had retained β€” exposed information about people who had no individual choice in the matter (their relatives' settings determined their own exposure).
  • That direct-to-consumer genetic testing companies' viability is now structurally tied to their cybersecurity posture in ways the original 2010s business model did not anticipate. 23andMe's bankruptcy followed multiple compounding pressures, but the post-breach customer-loss cohort was significant.

The case has also catalysed regulatory attention on consumer genetic-testing data: U.S. state laws specifically targeting DTC genetic data have proliferated post-23andMe, and the FTC has taken multiple enforcement actions against genetic-testing operators for inadequate security.

Financial impact

Reported costs in USD

Total reported loss
50.0M
USD Β· $50,000,000
  • Business loss$20.0M
  • Remediation$30.0M

Timeline

  1. Attackers begin testing credential pairs from prior breaches against 23andMe accounts. Approximately 14,000 accounts are directly compromised over the following months.

  2. Attackers begin systematically scraping ancestry profile data via the 'DNA Relatives' feature β€” which allows users to view profile information for genetic matches. Each compromised account exposes information about dozens to thousands of relatives' profiles.

  3. User-forum persona 'Golem' offers a sample of '~1 million Ashkenazi Jewish 23andMe profiles' for sale, then expands to 'all 23andMe data'. The dataset includes names, profile photos, ethnicity estimates, and ancestry information.

  4. 23andMe publicly confirms unauthorised access via credential stuffing. Initial scope: 14,000 directly compromised accounts.

  5. 23andMe revises scope: 6.9 million users had profile data exposed via the DNA Relatives feature β€” roughly half of 23andMe's customer base.

  6. 23andMe agrees to a $30M class action settlement covering U.S. users.

  7. 23andMe files for Chapter 11 bankruptcy protection. The breach is cited as a contributing factor to subsequent customer loss and litigation costs.

  8. UK ICO and Canadian Privacy Commissioner jointly find 23andMe's data protection inadequate and order remediation.

Sources

  1. blog.23andme.comhttps://blog.23andme.com/articles/addressing-data-security-concerns
  2. ico.org.ukhttps://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2025/06/joint-investigation-into-23andme-finds-genetic-data-was-not-adequately-protected/
  3. justice.govhttps://www.justice.gov/usao-ndca/pr/23andme-agrees-pay-30-million-resolve-class-action

Related incidents

Credential stuffingContained

Snowflake customer-account credential-stuffing campaign (UNC5537, 2024)

A threat cluster tracked as UNC5537 / ShinyHunters used credentials harvested by infostealer malware to log into ~160 Snowflake customer tenants that lacked MFA. Victims included AT&T, Ticketmaster, Santander, LendingTree, Advance Auto Parts, Neiman Marcus, and Bausch Health. Ticketmaster alone exposed data for ~560 million users.

Victim
Snowflake customer tenants (~160 organisations: AT&T, Ticketmaster, Santander, LendingTree, Advance Auto Parts, Neiman Marcus, Bausch Health, et al.)
Records
560.0M
EspionageContained

Microsoft Storm-0558 signing-key theft and US government email access (2023)

China-based Storm-0558 forged authentication tokens using a stolen Microsoft consumer signing key and read email at approximately 25 organisations β€” including the US State Department, the Department of Commerce, and the U.S. Ambassador to China. The 'cascade of errors' that enabled it became a defining case for cloud-provider key custody.

Victim
Microsoft customers (US State Department, Department of Commerce, ~25 organisations)