Case 0ADC44 · Famous breaches · L3 Applied

Your data warehouse is being copied

Practise as: Incident drillLevel: L3 Applied

Live alertJune 2024: Snowflake and Mandiant publish UNC5537 IOCs. Your LOGIN_HISTORY shows password-only user SVC_REPORTING logging in from a VPS IP, then CREATE TEMPORARY STAGE, COPY INTO on customer tables, and GET.

  1. 01 What happened?
  2. 02 What is the impact?
  3. 03 What do you do?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Snowflake itself was not breached: UNC5537 reused creds stolen by infostealers, some dating back years, on accounts without MFA
  2. Stage, COPY INTO and GET is bulk exfiltration: treat the customer tables as stolen and expect an extortion demand
  3. Disable the user, rotate all Snowflake creds, add network policies and MFA, and preserve LOGIN_HISTORY and QUERY_HISTORY
  4. Scope from ACCOUNT_USAGE: which tables, how many rows, which IPs; then find the infected machine that leaked the password
  5. Start notification and legal work; victims included AT&T, Ticketmaster and Santander, so regulators and press will move fast

If the interviewer pushes back

  • The leaked password came from a contractor's personal laptop. How do you stop third-party infostealer infections exposing your SaaS?

More Famous breaches cards

All Famous breaches cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09