11 min read
Credential stuffing fines: 23andMe, PayPal, Ring and more
23andMe, PayPal, Dunkin', Ring, Roku, DraftKings and more. What each credential stuffing attack cost, and what regulators said should have stopped it.
By BreachDetect Research
On this page
When customer accounts get taken over with reused passwords, a company's first reaction is often that it isn't really their breach. The customers reused their passwords, the company's systems weren't hacked, and the passwords came from somewhere else.
Regulators stopped accepting that some time ago. In June 2025 the UK Information Commissioner's Office described credential stuffing as "widely recognised as a prominent cybersecurity risk to organisations offering online account-based products and services," and fined a company for not planning for it. The New York Attorney General, the US Federal Trade Commission, New York's financial regulator, Canada's privacy commissioner and South Korea's privacy regulator have all said much the same.
Here's what credential stuffing has cost the companies on the receiving end, case by case, and what each regulator said should have stopped it. We've used regulators' decisions, court records and the companies' own breach notices wherever we could, and said so where a figure only comes from press reports.
The cases at a glance
| Company | Attack | Accounts | What it cost |
|---|---|---|---|
| 23andMe | 2023 | About 14,000 accessed, data on 6.9 million people | £2.31m UK fine, $46.75m class settlement, $18m to US states, bankruptcy |
| Ring | 2019 to 2020 | More than 55,000 | $5.8m FTC order, which also covered other allegations, and compulsory MFA |
| GS Retail | 2024 to 2025 | Data on 1.66 million users | 12.8bn won fine, about $9.3m |
| PayPal | 2022 | 34,942 | $2m penalty from New York's financial regulator |
| Dunkin' | 2015 to 2018 | More than 300,000 | $650,000 to New York, plus refunds |
| DraftKings | 2022 | About 68,000 | About $600,000 taken from customers, which DraftKings paid back |
| Roku | 2024 | About 591,000 | Refunds, and 2FA switched on for every account |
| Chick-fil-A | 2023 and 2026 | 71,473, then 13,322 | Balances restored, two lawsuits |
| The North Face | 2020 to 2025 | Four attacks, about 248,000 | Passwords disabled, stored cards erased |
23andMe
This is the case regulators now point to, and the most expensive by a distance.
Between April and September 2023, attackers logged into 23andMe accounts using what the ICO called "reused login credentials that were stolen from previous unrelated data breaches." The company counted about 14,000 accounts, less than 0.1% of its customers. But 23andMe had a feature called DNA Relatives that let customers see details of people they were genetically related to. Through those 14,000 accounts the attackers scraped profiles of about 5.5 million DNA Relatives users and 1.4 million Family Tree users. 23andMe told Canada's privacy commissioner that 6,984,430 people were affected worldwide.
The ICO's penalty notice spells out what went wrong:
- Only 0.2% of customers had turned on multi-factor authentication, and 21.5% signed in with Google or Apple. "Notably none of those accounts were successfully accessed by the threat actor."
- 23andMe did check passwords against known leaks, but against "only 20,000 passwords collected in 2021" out of a public dataset of about 500 million.
- The company's own chief product officer had argued for compulsory MFA before the breach.
- The breach "could have been avoided if MFA had been mandated on all customer accounts."
23andMe reset every password in October 2023 and made MFA compulsory the following month.
What it cost. The ICO fined it £2.31 million in June 2025. It had proposed £4.59 million and cut the figure because of the company's "significantly deteriorated financial position." The UK Information Commissioner, John Edwards, said: "23andMe failed to take basic steps to protect this information. Their security systems were inadequate, the warning signs were there, and the company was slow to respond."
Canada's privacy commissioner found that 23andMe "did not take into account the risk of credential stuffing in developing its safeguards, despite the fact that credential stuffing was widely known to be a common form of attack." It issued no fine.
In the US, a court set the class action settlement at $46.75 million in July 2026. The same month, 42 states announced an $18 million settlement. Their findings included "failing to employ safeguards against credential stuffing attacks, including comparing passwords against blocklists of known breached passwords or requiring multifactor authentication." Arizona's Attorney General said the company "first denied a breach and then, once it confirmed the breach, blamed consumers."
By then 23andMe was gone. It filed for bankruptcy in March 2025, saying it intended "to resolve all outstanding legal liabilities stemming from the previously disclosed October 2023 cyber incident" through the process. Its assets were sold that July for $305 million to TTAM Research Institute, a nonprofit led by its co-founder Anne Wojcicki. The breach wasn't the only reason the company failed, since it had been losing money for years. But the claims from the breach were the liabilities the bankruptcy was meant to deal with.
Ring
Ring, Amazon's doorbell camera company, is the case where the FTC made MFA a condition of settling. The FTC's 2023 complaint said credential stuffing and brute force attacks "are well-known forms of attack," and that more than 55,000 US customers had their accounts compromised between January 2019 and March 2020. For a company whose product is a camera inside people's homes, that's about as bad as an account takeover gets.
What it cost. Ring agreed to an order that required a $5.8 million payment and multi-factor authentication on customer accounts. The money also covered separate allegations that employees had viewed customers' videos, so not all of it was about credential stuffing.
GS Retail
In August 2026 South Korea's Personal Information Protection Commission fined GS Retail 12.836 billion won, about $9.3 million, plus a separate 3 million won fine. Credential stuffing attacks on its GS SHOP shopping site ran from June 2024 to February 2025, and on its GS25 convenience store app from December 2024 to January 2025. Data on 1,581,026 GS SHOP users and 79,128 GS25 users leaked.
The regulator's main complaint was that nobody noticed. It said GS Retail "failed to implement measures to detect or block repeated login attempts originating from the same IP address" and missed "a surge in login attempts and failures." The GS SHOP attacks went on for eight months.
PayPal
PayPal's case started with a product decision. In October 2022 it put Form 1099-K tax documents into customer accounts with customers' full Social Security numbers visible. In early December, according to New York's Department of Financial Services, a post appeared online reading "PP EXPLOIT TO GET SSN." The next day PayPal saw a spike in login attempts. Between 6 and 8 December, attackers got into 34,942 accounts.
What it cost. PayPal offered affected customers two years of credit monitoring. In January 2025 the Department fined it $2 million. Its press release said: "Notably, the company did not require customers to use multifactor authentication or use controls such as CAPTCHA or rate limiting to help prevent unauthorized access." When PayPal did switch on CAPTCHA and rate limiting, the consent order says, they "successfully stopped the automated account access."
Dunkin'
Dunkin' is the clearest case of staying quiet costing more than the attack. According to the New York Attorney General's 2019 lawsuit, Dunkin's app developer told it in 2015 that 19,715 accounts had been compromised in a five-day sample. Dunkin' didn't tell those customers, reset their passwords or freeze the money on their stored-value cards. In late 2018 a vendor reported that more than 300,000 accounts had been accessed. Dunkin' told customers that someone had "attempted" to log in.
What it cost. Dunkin' settled in September 2020, paying $650,000 in penalties and costs and agreeing to notify customers, reset their passwords and refund stolen balances. Attorney General Letitia James said: "For years, Dunkin' hid the truth and failed to protect the security of its customers, who were left paying the bill."
DraftKings
In November 2022, attackers logged into about 68,000 DraftKings accounts, according to the company's breach notice. In a sentencing announcement, the US Department of Justice said they took about $600,000 from roughly 1,600 accounts by adding their own payment method and withdrawing the balance, and sold access to other accounts through online "shops." DraftKings restored the money customers lost.
This is one of the few cases where the attackers were caught. Three men were sentenced in New York: Joseph Garrison to 18 months in January 2024, Kamerin Stokes to 30 months in April 2026, and Nathan Austad to 18 months in June 2026. US Attorney Jay Clayton said they had compromised "over 60,000 users by purchasing their already stolen credentials on the darkweb and utilizing their previous passwords from other websites." The prosecutions came well after DraftKings had already paid customers back.
Roku
Roku had two attacks in two months. Its first notice, sent in March 2024, covered logins from December 2023 to February 2024. The count reported from its filing with Maine's Attorney General was 15,363. In April it announced a second attack affecting about 576,000 more accounts. In "less than 400 cases" attackers used saved payment methods to buy streaming subscriptions and Roku hardware, and Roku refunded or reversed those charges.
What it cost. Mainly refunds, plus a change it could have made earlier. After the second attack Roku "enabled two-factor authentication (2FA) for all Roku accounts," more than 80 million of them.
Chick-fil-A
Between December 2022 and February 2023, attackers used credentials "obtained from a third-party source" against Chick-fil-A's app and website. The figure reported from its Maine filing was 71,473 customers. Chick-fil-A forced password resets, removed stored cards, froze loaded funds, restored customers' balances and added extra rewards. A lawsuit over the breach was reportedly settled with five individual plaintiffs for $210,000 in total.
In June 2026 it happened again, over three days this time. Chick-fil-A gave the same response, with the reported count at 13,322 customers. A class action over the second attack was reportedly withdrawn in September.
The North Face
The North Face has now notified customers about credential stuffing four times. In October 2020 attackers got into 34,582 accounts and, in some cases, made purchases. In August 2022 it was 194,905 accounts. In March 2025 there was a third attack across thenorthface.com and timberland.com, and in April 2025 a fourth, which the company called a "small-scale credential stuffing attack." Press reports put those two at about 15,700 and 2,861 accounts.
In 2020 and 2022 VF Outdoor, which owns the brand, disabled the affected passwords and erased stored payment details, and in 2020 it added limits on login attempts. We found no regulator action over any of the attacks. But four notices in five years is the strongest argument in this list that resetting passwords after the fact doesn't fix the underlying problem.
The business version: Snowflake
Credential stuffing isn't only a consumer problem. In 2024 attackers broke into the Snowflake cloud data accounts of about 165 organisations. Mandiant found that "at least 79.7% of the accounts leveraged by the threat actor in this campaign had prior credential exposure." The credentials came from infostealer infections on employees' and contractors' computers, some dating back to November 2020, and the accounts didn't use MFA.
The US Department of Justice says victims paid more than $2.5 million in ransoms. AT&T's $177 million class settlement includes $28 million for its part in the Snowflake incident. Snowflake has since phased out sign-ins with a password alone. It made a second factor compulsory on its web interface from September 2025, then blocked password-only sign-ins for every account between August and October 2026.
What regulators said should have stopped it
Read the decisions side by side and the same few points keep coming up.
- Multi-factor authentication. The ICO said MFA would have prevented the 23andMe breach. The FTC wrote it into Ring's order, and New York's financial regulator criticised PayPal for not requiring it.
- Checking passwords against known leaks. The ICO, Canada's privacy commissioner and the 42 US states all faulted 23andMe for a weak breached-password check.
- Noticing the attack. GS Retail was fined for missing "a surge in login attempts and failures," and the US states cited 23andMe's failure to act on "a massive spike in login attempts."
- Basic friction on the login page. New York's financial regulator named CAPTCHA and rate limiting in the PayPal case.
- Telling customers the truth, quickly. The Dunkin' settlement was mostly about what the company didn't say.
None of these is new. The New York Attorney General published a business guide to credential stuffing covering all of them in January 2022, after finding more than 1.1 million compromised customer accounts at 17 companies. We cover the same defences in how credential stuffing works and what stops it.
The costs that don't make the headlines
Fines are the part that gets reported. Most of the money goes elsewhere. Roku, Chick-fil-A, DraftKings and Dunkin' all refunded customers or restored their balances. PayPal paid for two years of credit monitoring. Then there are the support staff answering angry customers, the lawyers, and the breach notices to regulators in each state where affected customers live.
Then there are the customers who leave. In a 2025 survey for the fraud prevention company Sift, 75% of US consumers said they would stop using a site after an account takeover. Javelin Strategy & Research estimated US account takeover losses at more than $15 billion in 2025, the most expensive type of identity fraud it tracks.
What to take from this
Every case on this list started with passwords that leaked somewhere else. In none of them did the attackers need a flaw in the company's login system. What regulators judged was how each company prepared for a risk everyone already knew about. Some had MFA as an option nobody used. One had a breached-password check too small to matter. Others didn't notice a surge in failed logins, or didn't tell customers when they did.
The cheapest point to deal with a leaked customer password is before anyone tries it. Our study of 40 big consumer websites found a median of 1,380 new customer logins posted for each site in a single month. How to check if your customers' passwords have leaked covers the free and paid ways to find yours, and our free account takeover check shows how many there are for your site right now.
