company logo

Product

Our Product

We are Reshaping the way Developers find and fix vulnerabilities before they get exploited.

Solutions

By Industry

BFSI

Healthcare

Education

IT & Telecom

Government

By Role

CISO

Application Security Engineer

DevsecOps Engineer

IT Manager

Resources

Resource Library

Get actionable insight straight from our threat Intel lab to keep you informed about the ever-changing Threat landscape.

Subscribe to Our Weekly Threat Digest

Company

Contact Us

Have queries, feedback or prospects? Get in touch and we shall be with you shortly.

loading..
loading..
loading..
Loading...

Healthcare

loading..
loading..
loading..

23andMe Blames VICTIMS for Massive 6.9 M Healthcare Data Breach Fallout

23andMe, after facing over 30 lawsuits following a massive healthcare data breach impacting 6.9 million users puts blame on it's victims

03-Jan-2024
3 min read

In a twist of blame-shifting dynamics, 23andMe, after facing over 30 lawsuits following a massive healthcare data breach impacting 6.9 million users, is now blatantly deflecting blame onto its victims and is accused of downplaying the severity of the breach.

Breach Overview

Hackers initiated the breach by accessing 14,000 accounts through credential stuffing. The real impact unfolded as the attackers leveraged the DNA Relatives feature, compromising 6.9 million users' personal data.

Victim-Blaming Tactics

In a letter to victims, 23andMe deflects blame, alleging users' negligence in password management. The company argues that security incidents unrelated to 23andMe contributed to the breach, attempting to absolve itself of responsibility.

Legal Perspective

Hassan Zavareei, representing the victims, criticizes 23andMe's attempt to blame users as "nonsensical." He argues that the company should have implemented safeguards against credential stuffing, considering the sensitive nature of the stored information.

User Backlash

Dante Termohs, a victim of the breach, expresses outrage, finding it "appalling that 23andMe is attempting to hide from consequences instead of helping its customers."

Data Sensitivity

23andMe's lawyers claim the stolen data is not harmful, lacking critical information like social security numbers or financial details. This assertion, however, faces skepticism from legal and cybersecurity experts.

Company Response

Following the breach, 23andMe reset all passwords and enforced multi-factor authentication, which was previously optional. However, critics argue that these measures were reactive, not proactive.

Legal Maneuvers

To deter class action lawsuits, 23andMe modified its terms of service. Legal experts describe these changes as "cynical," "self-serving," and a "desperate attempt" to protect the company from legal repercussions.

Expert Opinion

Zavareei emphasizes that millions were impacted, not due to recycled passwords but through the DNA Relatives feature. He dismisses 23andMe's blame game, asserting it does nothing for the compromised users.

Technical Implications

The breach sheds light on the vulnerability of 23andMe's security infrastructure. Analyzing the technical details reveals the hackers exploited credential stuffing, a well-known technique that should have been anticipated and prevented.

Credential Stuffing: An In-Depth Look

Credential stuffing involves using known passwords to breach accounts. In 23andMe's case, the initial 14,000 victims fell prey to this technique, leading to a cascading compromise of millions due to the interconnected DNA Relatives feature.

# Example Code: Basic Credential Stuffing Attack
def credential_stuffing(username, password):
    # Code logic for attempting login with provided credentials
    # If successful, gain unauthorized access to the account
    pass

Security Measures and Missteps

23andMe's reliance on user password management is a critical flaw. The company should have implemented proactive measures against credential stuffing, given the sensitive nature of the stored information.

Multi-Factor Authentication Implementation

The delayed enforcement of multi-factor authentication raises concerns about 23andMe's commitment to user security. This essential security layer should have been mandatory from the outset.

# Example Script: Enforcing Multi-Factor Authentication
if user_enrollment_status == 'breach':
    enable_multi_factor_authentication()

Legal Ramifications and Data Sensitivity

The assertion that the stolen data is harmless disregards the potential misuse of genetic and ancestry information. Legal experts argue that the compromised data still poses risks, challenging 23andMe's attempt to downplay the severity.

User Privacy Concerns

The breach raises profound concerns about user privacy, as genetic and health data can be exploited for various malicious purposes. The attempt to diminish the impact on users disregards the broader implications.