Skip to main content
NewsMay 23, 20242 min read

Snowflake Customer Data Breaches: When Credential Stuffing Becomes Supply Chain Risk

Snowflake customers faced widespread data breaches due to credential stuffing attacks. The incident reveals critical lessons about cloud security hygiene and third-party risk management.

By 3SN Editorial
#Snowflake#Credential Stuffing#Data Breach#Cloud Security#Identity
Snowflake Customer Data Breaches: When Credential Stuffing Becomes Supply Chain Risk
Cloud Security
May 23, 20243SN Newsroom

Snowflake Customer Data Breaches: When Credential Stuffing Becomes Supply Chain Risk

Snowflake customers faced widespread data breaches due to credential stuffing attacks. The incident reveals critical lessons about cloud security hygiene and third-party risk management.

Snowflake Customer Data Breaches: When Credential Stuffing Becomes Supply Chain Risk

TL;DR

  • Multiple Snowflake customers experienced data breaches due to credential stuffing attacks using stolen credentials.
  • Mandiant confirmed the attacks targeted Snowflake customer accounts, not Snowflake infrastructure itself.
  • Organizations must enforce MFA, rotate credentials, and audit third-party access to cloud data platforms.

The short version

Multiple Snowflake customers experienced data breaches in May 2024, but the root cause was not a vulnerability in Snowflake's platform. Attackers used credentials stolen by infostealer malware to execute credential stuffing attacks against customer accounts that lacked multi-factor authentication. Mandiant's investigation confirmed Snowflake's infrastructure remained secure; the compromise occurred at the customer identity layer.

This incident serves as a clear reminder that cloud security is a shared responsibility. The platform provider secures the infrastructure, but customers must secure their access credentials and authentication policies. Organizations storing sensitive data in cloud data warehouses must treat identity as the primary security boundary and implement controls accordingly.

Why this matters beyond a single product

The Snowflake breaches illustrate a broader pattern affecting all cloud services. As organizations migrate data to cloud platforms, the security model shifts from network-centric to identity-centric. When credentials become the keys to the kingdom, protecting those credentials becomes paramount. The attack vector here was not sophisticated: stolen credentials and automated login attempts. The defense is equally straightforward: multi-factor authentication and credential hygiene.

This incident also highlights the supply chain implications of cloud data platforms. Many organizations use Snowflake to aggregate data from multiple sources, meaning a single compromised account could expose data originating from numerous business partners. Third-party risk management must extend to cloud platform access and identity controls.

Practical next steps for teams

If your organization uses Snowflake, enable MFA immediately on all accounts without exception. Review access logs for the past 90 days looking for unusual login patterns, unfamiliar IP addresses, or unexpected query activity. Rotate all credentials, especially for accounts with administrative or broad data access permissions.

Beyond Snowflake, audit your broader cloud identity posture. Are MFA policies enforced consistently across all cloud services? Are service accounts and API keys rotated regularly? Do you monitor for credential leaks and stolen credentials in dark web markets? If you only have time for one action today, verify that multi-factor authentication is mandatory, not optional, on every cloud platform handling sensitive data.

3SN perspective

Identity is the new perimeter, and this incident proves why. Strong authentication is not just a compliance checkbox; it is the fundamental control protecting cloud data. Organizations need identity systems that are both secure and usable, ensuring MFA adoption without creating friction that drives users to work around controls. When authentication feels natural, compliance improves and risk decreases simultaneously.

What happened

In May 2024, multiple Snowflake customers reported data breaches stemming from credential stuffing attacks. Mandiant investigated and confirmed that attackers used credentials stolen from previous infostealer malware campaigns to access customer accounts lacking multi-factor authentication.

Who’s affected

Snowflake customers without multi-factor authentication enabled faced the highest risk. Organizations storing sensitive data in Snowflake environments without robust identity controls were directly impacted, with several major companies confirming breaches.

What to do now

  1. Enable multi-factor authentication on all Snowflake accounts immediately and verify enforcement across all users.
  2. Rotate all Snowflake credentials and review access logs for unauthorized logins or suspicious query activity.
  3. Audit third-party integrations and service accounts with access to Snowflake data platforms.

Technical analysis

Mitigations & recommendations

critical

Enforce multi-factor authentication

Require MFA for all Snowflake user accounts without exception. Review account settings to ensure MFA is mandatory, not optional.

critical

Rotate credentials and audit access

Change all Snowflake passwords immediately and review access logs for the past 90 days for signs of unauthorized access or unusual query patterns.

high

Implement network policies

Restrict Snowflake access to approved IP ranges and require VPN or private connectivity where possible to reduce exposure.

high

Review third-party integrations

Audit all service accounts, API keys, and third-party tools with Snowflake access. Remove unused integrations and rotate associated credentials.