Credential stuffing tests billions of stolen username and password pairs from prior breaches against other services, exploiting the common practice of password reuse. It differs from brute force attacks in that it uses real known credentials, not guessed ones, making it both highly scalable and difficult to detect. Multi-factor authentication is the strongest defence, since a correct password alone is no longer enough. Australian organisations that suffer unauthorised account access from credential stuffing may have Notifiable Data Breaches obligations.
Credential stuffing is not an attack that requires skill or sophistication. It requires only access to a large list of breached credentials, which are freely and widely available, and an automated tool to test them. That simplicity is exactly why it operates at such scale.
How credential stuffing works
The attack begins with a collection of credential pairs: usernames (often email addresses) and their associated passwords. These lists come from historical data breaches, security research disclosures and criminal markets. Major breaches of large consumer services have resulted in hundreds of millions of credential pairs becoming available. These lists are aggregated, deduplicated and sold or shared freely.
An attacker downloads or purchases a credential list relevant to their target, for example a list where the email addresses match the target service’s likely user base. They load these credentials into an automated tool that sends login requests to the target service’s authentication endpoint, testing each pair. If the user reused their password from the breached service at the target service, the login attempt succeeds.
Successful logins are harvested and used for account takeover. Depending on the type of service, the attacker may access stored payment methods, steal stored funds or loyalty points, extract personal information for identity fraud, or use the compromised account as a launching point for further attacks.
Modern credential stuffing tools are sophisticated. They rotate through different IP addresses and user agents to avoid simple rate limiting and IP blocking. They introduce delays between requests to mimic human behaviour. They handle multi-step authentication flows and CAPTCHAs with varying degrees of success.
Why it works at scale
Password reuse is the root cause. Despite widespread advice to use unique passwords for every service, a large proportion of users rely on a small number of passwords across many accounts. When one of those services is breached and the password is exposed, every other service where the user applied the same password becomes vulnerable.
The volume of available credentials makes the attack statistically effective even at low reuse rates. A credential list of 100 million pairs tested against a service where only 1% of the credentials are reused still yields one million successful authentications, which represents a significant breach of account security.
Automation is the other enabler. Manual testing of credentials is not practical at scale, but automated tools can test thousands of pairs per minute, making the attack economically viable even against targets that have some rate limiting in place.
Detection signals
Credential stuffing attacks produce distinctive signals that monitoring systems can detect.
Unusual login volume. A spike in login attempts, particularly failed ones, is the most basic signal. A sharp increase in failed authentication events across many different accounts is likely automated activity.
Unusual geographic distribution. Logins appearing from many different geographic locations simultaneously, particularly locations inconsistent with the user base, indicate automated attack traffic distributed across residential proxies.
New device or user agent patterns. Automated tools often produce consistent or unusual user-agent strings and access patterns that differ from the organisation’s normal authenticated user base.
Velocity from a single IP or IP range. Before attackers add proxy rotation, they may generate high request volumes from a single source.
Successful logins from unusual locations. Account takeover, once it occurs, may be visible as a login from a new country or device that the legitimate user has never used.
The most effective defences
Multi-factor authentication. MFA is the primary control against credential stuffing. If authentication requires a second factor that the attacker does not have, a correct username and password is not enough to gain access. For any service where account takeover would be harmful, MFA should be mandatory. Phishing-resistant MFA (FIDO2/passkeys) is more resistant than push-based MFA, which is vulnerable to MFA fatigue attacks.
Unique passwords per service. Eliminating password reuse removes the condition that credential stuffing depends on. Password managers make this practical: a password manager generates and stores a unique, strong password for every service, so the user only needs to remember one master password. Organisations can promote this through security awareness training.
Rate limiting and account lockout. Limiting the number of failed login attempts from a single IP address or across a single account in a period of time slows automated testing and makes it detectable. Account lockout after a threshold of failures is a common control, though it introduces a denial of service risk if the attacker deliberately locks out accounts.
CAPTCHA and bot detection. CAPTCHA challenges on login pages add friction for automated tools. Bot detection systems that fingerprint browser behaviour, analyse request patterns and assess risk scores can identify and block automated traffic before it reaches the authentication step.
Credential exposure monitoring. Services like Have I Been Pwned (haveibeenpwned.com) and commercial threat intelligence feeds allow organisations to check whether their users’ email addresses appear in known breach data. Proactively notifying users whose credentials appear in breach data and prompting password resets and MFA enrolment reduces the exposure window.
Monitoring for anomalous login patterns. Security monitoring should include detection rules for the signals described above: spikes in failed logins, unusual geographic distributions, new devices on established accounts, and high-velocity login events.
Australian reporting considerations
If a credential stuffing attack results in unauthorised access to accounts holding personal information, the Notifiable Data Breaches scheme assessment process applies. An organisation that becomes aware that user accounts may have been compromised must assess whether the breach is likely to result in serious harm to affected individuals. If so, notification to the OAIC and affected individuals is required.
Notification to users, regardless of the formal NDB assessment outcome, is generally considered good practice and supports user trust. Affected users should be notified to change their password and enable MFA, and should be advised to change the same password on other services if they have reused it.
Cybernion’s security advisory services include authentication security reviews, MFA implementation guidance and security awareness programme design.
Frequently asked questions
What is credential stuffing?
Credential stuffing is an attack that uses large collections of stolen username and password pairs, obtained from data breaches of other services, and tests them against a target service in an automated and high-volume way. It works because many people reuse the same password across multiple services. If a person’s credentials were exposed in a breach of one service, those same credentials may still work on their accounts at other services where they have reused the password. Credential stuffing is distinguished from brute force attacks by the fact that it uses real, known credentials rather than trying guessed or generated ones.
Why is credential stuffing such a widespread problem?
Billions of username and password pairs from years of data breaches are circulating in criminal markets and freely available repositories. Automated tools make it simple to test these credentials against a target service at scale, thousands of login attempts per minute. Password reuse is common because people find it difficult to remember many unique passwords. The combination of a large supply of valid credentials, low-cost automation, and widespread password reuse makes credential stuffing a persistent and high-volume threat that requires no sophisticated capability from the attacker.
How does credential stuffing differ from brute force and password spraying?
Brute force attacks generate and try large numbers of possible passwords against a known username, without using credentials from prior breaches. Password spraying tries a small number of common passwords against a large number of accounts, aiming to avoid account lockout. Credential stuffing uses specific username and password pairs known to have worked somewhere before, testing whether those exact pairs also work on the target. Brute force relies on guessing; credential stuffing relies on reuse; password spraying tries known-weak passwords across many accounts.
What are the main defences against credential stuffing?
Multi-factor authentication is the most effective single control because a valid username and password alone is not enough to complete authentication. Unique passwords for every service, managed through a password manager, eliminate the reuse that credential stuffing depends on. Rate limiting, CAPTCHA and device fingerprinting at the login page make large-scale automated testing detectable and expensive. IP-based blocking and velocity checks can detect and block unusual login volumes. Monitoring for anomalous login patterns, such as logins from new geographies or devices, helps detect successful compromises.
What are Australian reporting obligations if credential stuffing compromises accounts?
If a credential stuffing attack results in unauthorised access to accounts that hold personal information, the Notifiable Data Breaches scheme requires the organisation to assess whether the breach is likely to cause serious harm. If so, the OAIC and affected individuals must be notified. The organisation should also investigate to understand the scope of the compromise, reset affected credentials, and notify affected users to change passwords and enable MFA.
Sources:
- OWASP Credential Stuffing, OWASP Foundation, 2026
- Notifiable Data Breaches scheme, Office of the Australian Information Commissioner, 2026
- Implementing multi-factor authentication, Australian Signals Directorate, 2026
Last updated: 30 August, 2026
