Cyber Attacks•7 min read•

What Is Credential Stuffing? How Reused Passwords Get Exploited

What credential stuffing is and how it differs from brute force: how leaked passwords are tried on other sites, warning signs and the defences that work.

Data breaches happen constantly, and many never make the news. What is more dangerous than the leaked data itself is how it is used afterwards: leaked email and password pairs become "keys" that attackers try on other accounts. This guide explains credential stuffing, how it works and how to protect yourself.

What Is Credential Stuffing?

Credential stuffing is an attack in which username and password combinations stolen in one breach are tried in bulk on unrelated websites and apps.

The logic is simple: many people use the same password on several sites. A "name@example.com – password123" pair leaked from a shopping site may also open an email account, social media, a gaming platform or a forum.

Attackers do not sign in by hand. Millions of combinations are tried on hundreds of services with botnets and automated tools. OWASP lists credential stuffing as its own category among automated threats to web applications.

The key point: the attacker is not trying to crack today's password. They already hold an old password from a breach years ago that you have forgotten about but still use.

How the Attack Unfolds

  1. A breach happens. A platform's database is stolen. Even if passwords are hashed, weak ones are cracked quickly; in some breaches they leak in plain text.
  2. Combo lists circulate. Email + password lists are shared, sold and merged into ever larger lists.
  3. Automated attempts begin. Tools send bulk sign-in requests to other sites. Requests come from thousands of IP addresses and imitate normal users, which makes them hard to spot.
  4. Successful logins are sorted. The tool reports working combinations. The success rate looks low, but across millions of attempts it means hundreds or thousands of compromised accounts.
  5. Accounts are used or sold. Attackers shop, change payment methods, send spam and phishing, or sell the accounts in bulk.

Brute Force vs Credential Stuffing

Brute force Credential stuffing
Data tried Random character combinations Real leaked email-password pairs
Scale Usually one account Millions of accounts on hundreds of sites
Why it works Guessing the password The same password being reused
Detection Many failed logins, rate limits Hidden by distributed IPs and slow attempts
Weakness exploited Short, weak passwords Password reuse

Brute force forces a lock; credential stuffing checks whether a key you already have opens other doors. That is why a very strong password used everywhere survives brute force but is defenceless against credential stuffing. (See also how passwords are cracked.)

Why You Are a Target: The Domino Effect of Reuse

"Who would target me?" is the attack's best friend. Credential stuffing does not pick targets; everyone on the list gets tried.

  • Your email address is the username almost everywhere, so one breach produces a "test key" for your whole digital identity.
  • If you use the same password on 10 sites, your security equals the weakest of them.
  • A forum or magazine account may seem worthless, but if its email and password match your important accounts, the dominoes start to fall.
  • The most critical domino is your email account: every password reset link goes there.

Signs Your Account Was Targeted

  • A sign-in alert from an unknown city or device.
  • Your password suddenly stops working (the attacker may have changed it).
  • Password reset emails you did not request.
  • Unfamiliar activity: orders, sent messages, a changed recovery email or phone number.
  • Friends tell you they received suspicious links from you.
  • The account is temporarily locked after "too many failed attempts".

The Most Effective Defences

For individuals:

  • Use a unique password for every account. This single habit breaks the whole attack; a combination works on one site only.
  • Prefer long passwords. NIST SP 800-63B puts length ahead of complexity rules; 16 characters or more is a sensible target.
  • Use a password manager. It is the only practical way to manage a different long random password per site.
  • Turn on MFA. An authenticator app or passkey is the strongest option; SMS is better than nothing but weaker against SIM swap attacks.

For site and app owners:

  • Apply rate limiting, CAPTCHA and bot detection to sign-in attempts.
  • Check new passwords against known breached-password lists, as NIST SP 800-63B explicitly recommends.
  • Offer MFA and alert users about sign-ins from unusual locations or devices.

Unique Passwords and MFA

  • A unique password guarantees that a breach affects only one account. The dominoes stop at the first tile.
  • MFA blocks sign-in even if the password leaks. A credential stuffer usually has only the password.

Where possible use passkeys (FIDO2), which replace the password with a device-bound, phishing-resistant method. A password manager makes all this sustainable: the only thing you memorise is one long vault password.

Breach Checks and Proactive Steps

  • Check your passwords against breach lists. HIBP-based checks use k-anonymity: the full password is never sent, only the start of its SHA-1 hash. Our breach checker works this way.
  • Test your password's strength. The Password Strength Test analyses it in your browser and estimates crack time.
  • Change passwords when needed, not on a schedule. NIST SP 800-63B does not recommend forced periodic changes; if a password was in a breach, change it right away.
  • Treat your email account as the priority. Protect it with a long, unique password and MFA.

Frequently Asked Questions

My password appeared in a breach. What should I do first? Change it on that site and on every account where you used the same password. Then turn on two-step verification and check that your email account's recovery details have not been changed.

If my password is strong, am I safe from credential stuffing? No. If it is the same on another site and that site leaked, the attacker does not need to crack it. A password must be both strong and unique.

Does credential stuffing only target big platforms? No. Automated tools try lists on hundreds of sites one after another; a small forum can be a target too. What matters is whether your password is used elsewhere.

Is SMS two-step verification enough? It is far better than nothing and stops many automated attacks, but it is exposed to SIM swap attacks, so an authenticator app or passkey is safer.

Are password managers safe? Yes. Reputable managers keep the vault end-to-end encrypted so even the vendor cannot read it. Remembering one long vault password is far safer than juggling dozens of similar ones.

First Step: Switch to Unique Passwords

The most practical start is generating a unique, long password for every account. The Password Generator is built for this:

  • Passwords are generated in your browser with the cryptographically secure crypto.getRandomValues.
  • Nothing is sent to a server or stored.
  • Choose the length, character sets and presets (16, 24 characters and more).

Making your important passwords unique today is the most effective step against automated attack waves. If you have just learned about a breach, also read what to do after a data breach.

Generate Strong Credentials Instantly

Hardware-backed Web Crypto API with zero logging and zero server contact.

Open Password Generator →