How Credential Stuffing Attacks Work and How to Stop Them
You get an email saying someone logged into your food delivery account from another country, and you never shared the password with anyone. The most likely explanation is not a clever hacker targeting you.

You get an email saying someone logged into your food delivery account from another country, and you never shared the password with anyone. The most likely explanation is not a clever hacker targeting you. It is credential stuffing: an automated attack that takes usernames and passwords leaked from one website and tries them on hundreds of others.
I spend a good part of my week reading login logs for small businesses, and credential stuffing is the attack I see most often. It is cheap, fast and depends almost entirely on one human habit. Understanding how it works makes it much easier to stop.
How credential stuffing attacks work
The attack has four stages, and none of them require the attacker to know who you are.
- Collect leaked logins. When a website is breached, its list of email addresses and passwords often ends up for sale or shared freely online. Some of these combined lists contain billions of entries.
- Load them into a tool. Attackers use automated software that reads the list and sends login attempts to a target site, one pair after another.
- Spread the traffic. To avoid being blocked, the tool sends attempts through thousands of different IP addresses, often from hijacked home routers or rented proxy networks. Each address might try only a handful of logins.
- Use what works. Successful logins are saved and either used directly, for stored payment cards, loyalty points or gift card balances, or sold on as working accounts.
The success rate per attempt is low, typically somewhere between 0.1 and 2 percent. But at a million attempts, even 0.5 percent means 5,000 working accounts. That arithmetic is why the attack is so popular.
Credential stuffing is not the same as brute force
The two get confused, but the difference matters for defence.
| Feature | Brute force | Credential stuffing |
|---|---|---|
| Passwords tried | Guesses or every possible combination | Real passwords leaked from other sites |
| Attempts per account | Many, often thousands | Usually one or two |
| Beaten by a long password | Yes | No, if that password was reused |
| Beaten by unique passwords | Partly | Yes |
That third row is the uncomfortable one. A 20 character password with symbols gives you no protection at all against credential stuffing if you used the same one on a site that was breached.
Signs your account has been hit
Most victims find out after the fact. Watch for these warnings:
- An unexpected "new sign-in" or "new device" email from a service.
- A password reset email you did not request. This sometimes means an attacker tried, failed, and moved to the reset flow.
- Loyalty points, store credit or gift card balances that have disappeared.
- Orders, bookings or address changes you did not make.
- Your email address appearing in a public breach notification service or in a warning from your password manager.
Attackers often follow up a successful login with a convincing message to you, pretending to be the service. If you get an alert, go straight to the site by typing its address yourself. Our guide on how to recognize a phishing attempt covers the tells.
How to stop credential stuffing as an individual
1. Use a different password for every account
This single change defeats the attack completely. If every password is unique, a leak from one site gives an attacker nothing they can use anywhere else. Nobody can remember 80 unique passwords, so use a password manager to generate and store them.
2. Start with the accounts that matter most
Do not try to change everything in one evening. Spend 30 minutes on the five accounts that would hurt most if taken over: your main email, your bank, your phone carrier, your main shopping account with a saved card, and any account used to sign in to other services.
3. Turn on two-factor authentication
Even with a correct password, an attacker cannot log in without the second factor. An authenticator app or a hardware key is far stronger than SMS codes, which can be intercepted through SIM swap fraud. Our walkthrough on how to set up a hardware security key covers the strongest option.
4. Check for leaks
Most password managers now flag passwords that appear in known breaches. Act on those alerts within a day or two. Leaked lists start circulating quickly.
Rotating passwords every 90 days does not help much here
A lot of workplaces still force staff to change passwords every three months, and many people believe this protects them. For credential stuffing, it mostly does not. People faced with forced rotation tend to make small, predictable changes, such as Summer2026 becoming Autumn2026, or adding 1 to the end. Attack tools try those variations automatically.
Current guidance from national standards bodies has moved away from scheduled rotation for this reason. Change a password when there is evidence of a leak or compromise, and otherwise focus effort on making every password unique and adding a second factor. That combination does far more than a calendar reminder.
What small businesses should do
If you run a website with customer logins, your customers' reused passwords become your problem. A few practical defences:
- Rate limit by account and by IP. For example, lock further attempts on one account for 15 minutes after 5 failures, and throttle IPs that fail across many accounts.
- Add a challenge on suspicious logins. Show a challenge only when the login comes from a new device, a new country or an IP with a poor reputation, so normal customers are not annoyed.
- Check new passwords against breach lists. Many login systems can reject passwords that are known to be leaked at the moment a customer sets them.
- Offer two-factor authentication, and require it for staff and admin accounts.
- Watch the ratio of failed to successful logins. A sudden jump from a normal 5 percent failure rate to 60 percent is a classic sign of an attack in progress.
None of these need an expensive security product. Most hosting platforms and login plugins already include rate limiting and breach checks that are simply switched off by default. Spend an hour reviewing your login settings this month, write down what you changed, and set a reminder to look at the failed login numbers once a week. That small routine catches most attacks while they are still small.
Frequently asked questions
How do hackers get passwords for credential stuffing?
They use lists of usernames and passwords leaked in earlier data breaches. These lists are traded or shared online, sometimes combined into huge collections. The attacker does not need to guess your password; they already have the one you used somewhere else.
Does two-factor authentication stop credential stuffing?
Yes, in most cases. Even with your correct password, the attacker would also need your code or security key. App-based codes and hardware keys are much more resistant than SMS, so choose those where a service offers them.
What should I do if my account was accessed through credential stuffing?
Change the password on that account to a new, unique one and sign out all other sessions. Then change the same password everywhere else you used it, and turn on two-factor authentication. Check for unauthorised orders or changes and report them to the service.
More in Threats and Attacks
Threats and Attacks
Evil Twin Wi-Fi Attacks and How to Spot the Fake
You sit down in an airport with forty minutes to kill and your phone has already joined something called Airport Free WiFi.
Threats and Attacks
SIM Swap Attacks and How to Protect Your Number
Your phone drops to no service in the middle of a Tuesday afternoon.
Threats and Attacks
Juice Jacking and Whether Public USB Chargers Are Safe
Your phone is on 4 percent, your flight boards in 40 minutes, and the only free socket at the gate is a USB port built into the...