Saturday, November 21, 2026
AI desk
/
/
The Snowflake Hacker Just Pleaded Guilty: What It Means for Your Stolen Data

The Snowflake Hacker Just Pleaded Guilty: What It Means for Your Stolen Data

Connor Moucka pleaded guilty August 5 to breaching 165 organizations and exposing 100M+ people’s data. Here’s what was taken and what to do now.
Last updated
August 10, 2026
9 min read
Fact-checked

Photo: TechJournal

Share

Quick Answer

Connor Riley Moucka pleaded guilty on August 5, 2026, in federal court in Seattle to breaching 165 organizations and exposing records belonging to at least 100 million people. The breach succeeded because affected accounts had no multi-factor authentication. If you used AT&T, Ticketmaster, Santander, or LendingTree in 2024, place a credit freeze and enable MFA on every account that supports it.

Key Takeaways

  • Connor Moucka, 26, of Kitchener, Ontario, pleaded guilty August 5, 2026, to computer fraud, wire fraud, aggravated identity theft, and conspiracy; he faces up to 32 years in prison and is scheduled to be sentenced October 27, 2026.
  • The campaign breached at least 165 organizations and exposed records tied to at least 100 million people, with confirmed victims including AT&T, Ticketmaster, Santander Bank, LendingTree, Advance Auto Parts, and Neiman Marcus.
  • The attacks succeeded entirely through stolen credentials and absent MFA, not through any vulnerability in Snowflake’s platform itself, according to independent investigations by Mandiant and CrowdStrike.
  • Moucka and co-conspirators collected more than $2.5 million in ransom payments and caused victim companies over $9.5 million in total losses, according to the plea agreement; Moucka personally received at least $495,000.
  • Snowflake is completing a phased mandatory MFA rollout between August and October 2026; consumers affected by the underlying breaches should place a credit freeze and monitor financial accounts now.

What exactly did Connor Moucka plead guilty to?

Connor Riley Moucka pleaded guilty on August 5, 2026, in the U.S. District Court for the Western District of Washington, admitting to computer fraud, wire fraud, aggravated identity theft, and a related conspiracy count tied to the 2024 breaches of Snowflake customer accounts. The plea covers four of the eleven counts in the federal indictment originally unsealed in November 2024.

Moucka admitted that the criminal activity ran from February through October 2024, that he personally received at least $495,000 from ransom payments (which he has agreed to forfeit), and that he hacked under a variety of aliases, including Alexander Moucka, catist, ellyel8, judische, and waifu. He is 26 years old, from Ontario, and is scheduled to be sentenced on October 27. He faces a mandatory two years in prison on the identity theft count, to run consecutively with up to 30 years on the other three charges, for as much as 32 years total.

“In total, Moucka and his co-conspirators caused the victim companies more than $9.5 million in actual losses, which included ransoms paid and costs of responding to the breaches,” the plea agreement states. That figure covers direct ransom payments as well as the forensic, legal, and notification costs each breached organization incurred.

Which companies were breached, and whose data was exposed?

The Snowflake breach was not a single intrusion but a coordinated campaign across a large number of enterprise cloud accounts. Affected companies included AT&T, Ticketmaster/Live Nation, Santander Bank, LendingTree, Advance Auto Parts, Neiman Marcus, and Bausch Health. For US consumers, AT&T and Ticketmaster represent the widest individual exposure.

The stolen AT&T data covered calls and texts made by nearly all of AT&T’s wireless customers, approximately 109 to 110 million people, during a six-month window from May 1 to October 31, 2022, with a small number of records extending to January 2, 2023. The records exposed in that breach did not include names, Social Security numbers, or financial information, but they did include the phone numbers involved in each call and text, call duration, and cell site location data, which can reveal where a person traveled and communicated.

Ticketmaster had 560 million customer records exposed. The breach resulted in the exposure of a wide range of sensitive data, including personally identifiable information such as full names, addresses, phone numbers, financial records, call and text metadata in the case of AT&T, and partial payment card data in the case of Ticketmaster.

How did the attackers get in if Snowflake’s platform was not hacked?

The Snowflake breach succeeded through credential theft, not through a software vulnerability. Rather than exploiting a vulnerability in Snowflake’s platform, the threat actors used stolen credentials, harvested by infostealer malware such as Vidar, RISEPRO, and LummaC2, to log directly into customer Snowflake tenants that did not have multi-factor authentication enforced. Snowflake’s own infrastructure was not compromised. Investigations by Mandiant (Google) and CrowdStrike confirmed that the campaign was a large-scale credential-based account takeover operation targeting enterprise cloud data environments.

Researchers found that at least 79.7% of the accounts used in the campaign had prior credential exposure, some tracing back to infostealer infections from as early as 2020, with a few passwords left unrotated for as long as four years. This matters for consumers because those same infostealer families also target personal devices, and credentials stolen from a home computer years ago may still be active in enterprise systems today.

Mandiant’s investigation confirmed that Snowflake had offered MFA as a configurable option, but none of the affected organizations had turned it on. That finding placed responsibility partly on the enterprise customers who managed those accounts, and it has since driven Snowflake’s decision to enforce MFA by default.

Who else is charged, and what is the status of co-defendants?

The Snowflake investigation produced charges against more than one individual. Of the two men charged in 2024, only Moucka is in US custody. Co-defendant John Erin Binns remains outside it as of the court’s August 4 case update. John Erin Binns, a 24-year-old who had been living in Turkey, was arrested separately and faces additional charges related to a 2021 T-Mobile breach.

One of Moucka’s admitted co-conspirators is Cameron “Kiberphant0m” Wagenius, a US Army soldier who pleaded guilty in July 2025 to extorting AT&T and Verizon for their customer account data. Wagenius is set to be sentenced on September 3, 2026. The three cases together represent the most complete federal prosecution of the 2024 Snowflake campaign to date, though Binns remaining outside US custody means the legal process is not fully resolved.

What has Snowflake changed since the breach?

Snowflake has responded to the 2024 breaches with a phased mandatory authentication overhaul, though the timeline has extended over two years. The rollout follows three milestones: Milestone 1 (September 2025 through January 2026) required MFA for all Snowsight users with password-based authentication; Milestone 2 (May 2026 through July 2026) required all newly created human users to use MFA and prohibited new legacy service users; Milestone 3 (August 2026 through October 2026) will require all human users to use MFA for any password-based access, with all service users required to use key-pair, OAuth, PAT, or WIF authentication.

Snowflake states that the rapid evolution of identity-based threats has made it clear that traditional password-only login is no longer optimal, and that credential abuse is the top reason for unauthorized access according to the Verizon 2025 Data Breach Investigations Report. That said, reader and trial accounts are exempt from the mandatory MFA requirement, which means the policy does not yet cover every Snowflake account type. Consumers do not interact directly with Snowflake, but they benefit indirectly as the enterprises holding their data are forced to adopt stronger authentication.

What type of data is at risk, and what do the threat rankings look like?

Breached CompanyData Type ExposedApproximate RecordsPrimary Consumer Risk
AT&TCall/text records, cell site data~109–110 millionLocation inference, targeted phishing, surveillance
TicketmasterNames, addresses, partial payment card data~560 millionPhishing, fraudulent ticket scams, card fraud
Santander BankAccount data, customer/employee PII~30 millionAccount takeover, identity theft
LendingTree / QuoteWizardFinancial and insurance quote dataNot publicly confirmedTargeted financial fraud, loan scams
Advance Auto Parts / Neiman MarcusEmployee and customer PIINot publicly confirmedIdentity theft, credential stuffing

The most urgent risk for the majority of affected consumers is targeted phishing. Scammers may reference real details from the breach to make phishing attempts more convincing, which means fraudulent emails or text messages about your AT&T bill, a Ticketmaster refund, or a Santander account alert may contain accurate personal details that were taken in this campaign. Treat any unsolicited communication requesting login credentials or payment as suspect, and verify it by navigating directly to the company’s official website rather than clicking any link in the message.

What concrete steps should affected consumers take right now?

If you were an AT&T wireless customer between May 2022 and January 2023, a Ticketmaster user, a Santander Bank customer, or a LendingTree or QuoteWizard user, treat your personal data as compromised and act accordingly. The steps below address the highest-probability risks first.

  1. Place a credit freeze at all three major bureaus. A credit freeze is a stronger measure than a fraud alert because it prevents new credit accounts from being opened in your name entirely. Contact Equifax, Experian, and TransUnion individually. A freeze is free under federal law and does not affect your existing credit accounts.
  2. Check your credit reports for unauthorized accounts. Check your credit reports at all three bureaus through AnnualCreditReport.com and consider placing a credit freeze to prevent new accounts from being opened in your name.
  3. Enable MFA on every account that supports it. Enable MFA on every account that supports it, especially financial accounts, email, and social media. Use an authenticator app rather than SMS-based verification when possible, because SMS codes can be intercepted through SIM-swapping attacks.
  4. Change passwords on any account that shares credentials with a breached service. The attackers used infostealer-harvested credentials that were sometimes years old. If you reused a password from an AT&T, Ticketmaster, or Santander account on any other service, change it on every platform where it appears.
  5. Monitor financial accounts for unauthorized transactions. Set up transaction alerts for all financial accounts so that any unexpected charge triggers an immediate notification. Report unauthorized transactions to your bank or card issuer promptly.

If you believe your identity has already been used to open fraudulent accounts or file fraudulent tax returns, contact the FTC’s identity theft reporting portal at IdentityTheft.gov. The FTC provides a personalized recovery plan at no cost. For financial fraud that has already resulted in account losses, contact your bank’s fraud department directly and, if losses are significant, consult a consumer protection attorney. Do not attempt to pursue data recovery or legal action independently without professional guidance.

For more on related security threats, see Tails Linux Emergency Update Fixes Flaw That Could Deanonymize You: What to Do Now and Windows 11 Has a Hidden Device Tracker VPNs Can’t Block: What Is GDID and How to Stop It.

FAQ

Was Snowflake’s software hacked in the 2024 breach?

Snowflake’s platform was not exploited through any software vulnerability. Independent forensic investigations confirmed that the root cause was credential theft via infostealer malware infections on customer-managed devices, combined with the absence of MFA enforcement on customer Snowflake accounts. The breach was an account takeover campaign, not a platform compromise.

How do I know if my data was exposed in the Snowflake breach?

The most reliable method is to check whether you received a breach notification letter from any of the affected companies. If you were an AT&T mobile customer in 2024, you should assume your call records were compromised. If you purchased tickets through Ticketmaster, your data was likely exposed. You can also check your email address against known breach databases through services such as Have I Been Pwned, which aggregates publicly reported breach data.

Is the guilty plea the end of the Snowflake case?

Moucka’s guilty plea resolves his portion of the case, but the broader prosecution is not closed. Of the two men charged in 2024, only Moucka is in US custody. Co-defendant John Erin Binns remains outside it as of the court’s August 4 case update. Moucka’s sentencing is scheduled for October 27, 2026, and co-conspirator Cameron Wagenius is set to be sentenced on September 3, 2026.

Will Snowflake’s new MFA requirement prevent a repeat breach?

Snowflake’s mandatory MFA enforcement for all human users, with a phased rollout to block password-only sign-ins for every remaining human and service user, is scheduled to complete by October 2026. This addresses the specific gap that enabled the 2024 campaign. That said, reader and trial accounts remain exempt from the requirement, and mandatory MFA does not eliminate risks from phishing, session token theft, or social engineering. Consumers benefit indirectly as enterprises holding their data must comply, but the protection depends on each organization fully implementing the new controls.

What ransom amounts were paid in the Snowflake breach?

The plea agreement states that Moucka and his co-conspirators extorted 36 bitcoin, worth about $2.5 million US at the time, from at least three victims. Moucka personally obtained at least $495,000 from sales on cybercrime platforms such as BreachForums and Telegram, and he has agreed to forfeit those proceeds. Individual company ransom amounts vary; Bloomberg reported that AT&T paid approximately $370,000 in bitcoin to have the stolen data deleted, though AT&T has not publicly confirmed that figure.

For further context on corporate AI and data security developments, see OpenAI Paused Astra Development Over a ‘Critical’ Cyberattack Risk: What It Means for You and ClickFix Is Now Draining Mac Crypto Wallets: What the New macOS Attack Does and How to Stay Safe. For broader security patching news, see The August 2026 Android Security Update Is Out: How to Install It.

Share this guide
Facebook
X
LinkedIn
Written by
Priya Sharma is a cybersecurity analyst and tech writer who covers digital privacy, online safety, and creative technology tools. She holds a CompTIA Security+ certification and writes about making security accessible for non-technical audiences. She’s passionate about the intersection of AI and creative work.

In this article

The AI Brief

Guides like this, every Friday.

One email. No hype cycle.

Essential guides