Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Credential stuffing is an attack that tries IDs and passwords leaked from one service on other services. It is also called a password list attack. IPA and JPCERT/CC explain it as an attack that takes a list of IDs and passwords obtained somehow and tries them, with an automated program, one after another on services that have a login function.
How does credential stuffing work?
Imagine someone who picks up a lost bunch of keys and goes around the town trying them in front doors. If the owner of the keys uses the same key at many houses, one of the doors will open.
What marks this attack is that it does not guess passwords. It uses real combinations that were already used, so even a long and complex password lets the attacker in if it is reused. OWASP treats it as a kind of brute-force attack, differing in that stolen combinations are tried on other sites.
The cause of the damage is not a flaw in the service that was tried, but the reuse of information that leaked from another service. So even if your own side is not at fault, members' accounts can be taken over. The background of unauthorized logins caused by reuse is on the password reuse page.
Why does credential stuffing matter?
In a survey IPA published in 2014, about a quarter of people (25.4%) reused the same password as on a service involving money. The most common reason for reuse was "because I forget my passwords" (64.1%). It is an old survey, but useful as a figure showing how reuse spreads.
As measures on the user's side, JPCERT/CC lists not reusing passwords, login notifications, checking login history and using two-step login. OWASP also names multi-factor authentication as its first measure. IPA also points to passkeys, which do not use a password.
On the operator's side, rate limiting slows traffic that tries many logins in a short time. If you can offer two-step login on the member login screen, it helps reduce takeovers. For a look at what your own site shows from outside, the free URL check reads only public information.
Related terms
- Brute-force attack: an attack that guesses by trying passwords one after another.
- Password spraying: trying common passwords a few at a time across many accounts.
- Two-step login: a mechanism that asks for one more check in addition to the password.
- Passkey: a way to log in by fingerprint or face, without a password.
Next step
The detailed background of unauthorized logins caused by reuse is on the password reuse page. The order for protecting logins as a whole is in unauthorized access measures. To talk about protecting member logins, contact us.
Frequently asked questions
What should I do first if I have been hit by credential stuffing?
Change the password of the account you noticed, and also change any other service that uses the same password. Check the login history and set up two-step login. If your site has members, the operator checks the extent of the effect.
Does a complex password prevent credential stuffing?
No. This attack uses real combinations that were already used, so complexity does not matter and reuse is the cause. Use a different password for each service, and add two-step login.
Frequently asked questions
What should I do first if I have been hit by credential stuffing?
Change the password of the account you noticed, and also change any other service that uses the same password. Check the login history and set up two-step login. If your site has members, the operator checks the extent of the effect.
Does a complex password prevent credential stuffing?
No. This attack uses real combinations that were already used, so complexity does not matter and reuse is the cause. Use a different password for each service, and add two-step login.