Credential Stuffing Attacks
Automated tools test billions of username-and-password pairs stolen from data breaches across hundreds of services simultaneously, silently taking over accounts where victims reused passwords.
Last reviewed: 1 June 2026
What this scam is
Credential stuffing is a large-scale automated account takeover technique that exploits the widespread human habit of reusing the same username and password across multiple online services. Attackers obtain vast databases of stolen credentials — typically sourced from previous data breaches at companies that stored passwords poorly — and use automated software to test those pairs against many popular websites and apps simultaneously.
Unlike brute-force attacks, which try random password guesses, credential stuffing uses real credentials that were previously valid somewhere. This makes the success rate significantly higher, even though it is still a small percentage of attempts in absolute terms. When services hold hundreds of millions of accounts, even a one-percent success rate against a leaked credential list of ten million pairs means tens of thousands of compromised logins.
Victims typically have no warning that an attempt is in progress. The attack is silent and automated, and the first sign of compromise is usually a notification that their account has been accessed from an unfamiliar device or location — often after the attacker has already extracted value from the account. Because the attack exploits credential reuse rather than any weakness in the target service's own security, the responsibility for defence lies primarily with the account holder.
How it works
The process begins with a credential list: a file containing millions of email-address-and-password pairs compiled from one or more data breaches. These lists are traded and sold in criminal markets and are updated continuously as new breaches occur.
Attackers load the list into automated software — known as credential stuffing tools — that submits login requests to target websites in a distributed manner, often routing traffic through residential proxy networks to disguise the volume and avoid IP-based rate limiting.
When a valid combination is found on a target service, the tool flags it. The attacker then logs in manually or through further automation to extract value: check the account balance, drain a stored gift card balance, place orders with saved payment methods, access stored personal documents, or use the account as a launchpad for further fraud. High-value accounts — banking, cryptocurrency exchanges, e-commerce with stored cards — are prioritised.
Many credential stuffing campaigns are run against dozens of services simultaneously, maximising the return from a single leaked dataset. The scale of some attacks means that a breach at a relatively obscure service years ago can result in compromises at major financial institutions today.
Why this scam works
Password reuse is extremely common because managing unique passwords for every service is cognitively demanding without a dedicated tool. People naturally gravitate toward memorable passwords that they can use repeatedly, especially for services they consider low-risk — not realising that a breach at any one of them exposes all accounts where the same credentials were used.
Automation makes the attack economically viable: the marginal cost of testing an additional credential pair is near zero once the tooling is set up. Residential proxy networks make IP-based blocking difficult. And because the credentials being tested were genuinely valid at some point, sophisticated fraud-detection systems trained on 'normal' user behaviour have to work harder to distinguish a credential stuffer from a legitimate user.
A typical pattern
A person used the same email and password combination for their email, a streaming service, and their supermarket loyalty account. The streaming service suffered a data breach several years earlier. An automated tool tested the stolen credentials against a major retailer and found a match. The attacker logged in, changed the delivery address, and placed an order using the stored payment method. The person only discovered the compromise when they received an order confirmation for items they had not bought.
Common red flags
- Login alert from a device or location you do not recognise
- Order confirmation for a purchase you did not make
- Loyalty points balance unexpectedly depleted
- Password reset email arriving that you did not request
- Account activity history showing sessions you did not initiate
- Notification that your email or recovery details have been changed
- Your email appears in a breach-notification service result
Sanitized example messages
Illustrative, sanitized examples. Personal details are replaced with placeholders such as [phone number] and [fake link].
New sign-in to your [service] account from [device] in [location]. If this wasn't you, secure your account at [link].
Your order [order number] for [amount] has been confirmed. Your delivery address is [unfamiliar address].
Your loyalty points balance has changed. [Number] points were redeemed on [date] at [location].
Your [service] account password was recently changed. If you did not make this change, click here.
Common variations
- Password spraying — a lower-volume variant that tests a small number of common passwords against many accounts to avoid lockouts
- Account checker tools — consumer-facing criminal tools that let buyers verify whether purchased credentials work on a specific service
- Combo list attacks — attacks using merged lists from multiple breaches for broader coverage
- API stuffing — targeting mobile app API endpoints rather than web login forms to bypass browser-based protections
How to verify before you act
Check whether your email address has appeared in known data breaches using a reputable breach-notification service. If your credentials appear in a breach, change the password on the affected service immediately and on every other service where you used the same password.
Log into your important accounts and review the recent activity or login history section. Look for logins from unrecognised locations, devices, or IP addresses. Many services send email alerts for new device logins — enable these if the option exists.
If you have been using the same password on multiple services for a long time, treat it as compromised and rotate it. A password manager makes it practical to maintain unique, strong passwords across hundreds of accounts.
Payment methods used
- Stored card charges on compromised e-commerce accounts
- Gift card balance drain
- Cryptocurrency account drain
- Direct bank account access via compromised banking login
Who is usually targeted
- Anyone who reuses passwords across multiple services
- Holders of e-commerce accounts with stored payment methods
- Cryptocurrency exchange account holders
- Loyalty programme members with redeemable points balances
What to do immediately
- Change the compromised password immediately on the affected service and every service where you used the same password
- Enable two-factor authentication using an authenticator app on all important accounts
- Review recent account activity and report any unauthorised transactions to the relevant service
- Contact your bank or card issuer if stored payment methods were used without your authorisation
- Check your email address on a reputable breach-notification service and act on any findings
- Begin using a password manager to maintain unique passwords going forward
How to prevent it
- Use a unique, randomly generated password for every account, managed by a password manager
- Enable login alerts on all important accounts so new device access is flagged immediately
- Use an authenticator app for two-factor authentication — this stops credential stuffing even when credentials are valid
- Subscribe to a breach-notification service and act promptly on any alerts
- Prioritise password uniqueness on financial, email, and healthcare accounts above all others
Evidence to preserve
- Screenshots of unauthorised login alerts or activity notifications
- Order confirmations for purchases you did not make
- Login history from affected account security settings
- Any breach-notification results showing your email in leaked data
Where to report it
- Action Fraud (UK) — UK national fraud & cybercrime reporting centre
- FTC ReportFraud (US) — US Federal Trade Commission fraud reports
- FBI IC3 (US) — US Internet Crime Complaint Center
- Scamwatch (Australia) — Australian competition & consumer reporting
- Your bank's fraud line — Use the number on the back of your card or in your banking app — never a number the caller gives you
Always verify reporting routes and emergency contacts on the official government or agency website for your country.
Frequently asked questions
How is credential stuffing different from hacking?
Credential stuffing does not require breaking into the target service. It uses credentials already stolen from a different service and tests whether they also work somewhere else. The vulnerability is password reuse by the account holder, not a weakness in the target platform.
Why would a breach at a small website affect my bank account?
If you used the same email and password on both the small website and your bank, the credentials stolen from the small website can be tested against your bank. The breach database does not care where the credentials came from — automation tests them everywhere.
Does two-factor authentication stop credential stuffing?
Yes, app-based two-factor authentication stops a credential stuffing attack even if the attacker has your correct password — they cannot complete the login without the second factor from your device. This is one of the most effective and accessible defences available.
How often do credential stuffing attacks succeed?
Success rates vary widely. On services with good login protections, the success rate may be very low. But because attack volumes are enormous — billions of credential pairs tested across many services — even a tiny percentage success rate produces significant numbers of compromised accounts.
My password is complicated — am I safe?
Complexity alone does not protect against credential stuffing. If you used the same complex password on two services and one of those services suffered a breach, your complex password is in the breach database. Uniqueness matters more than complexity for protection against this attack.