NEW
An attack using leaked username-password pairs to gain unauthorized access across multiple services.
DESCRIPTION
Credential stuffing automates the use of breached credentials to compromise accounts on different sites, exploiting password reuse. Attackers deploy bots, proxies, and rotating IPs to evade detection and throttle limits. Defenses include MFA, anomaly detection, device fingerprinting, and rate limiting. Credential hygiene via password managers and breach monitoring reduces risk. Organizations should implement layered controls and monitor account takeover indicators.
ALTERNATIVE DEFINITIONS
OWASP
Credential stuffing is the automated injection of breached username/password pairs to gain access to user accounts.
Emphasizes automation and use of breached credentials.
Wikipedia
Credential stuffing is a type of cyberattack where stolen account credentials, typically lists of usernames and passwords, are used to gain unauthorized access to user accounts.
Highlights stolen lists and unauthorized access.
Cloudflare
Credential stuffing attacks use bots to try multiple username and password combinations, exploiting password reuse across different services.
Focuses on bot-driven automation and reuse across services.
RELATED TERMS
Brute-Force Attack Password Reuse Multi-Factor Authentication Bot Mitigation Data Breach Rate Limiting Account Takeover CAPTCHA Password Manager
COMPETING TERMS
Password Spraying
KNOWLEDGE AREAS
Data Security Data Privacy & Compliance Observability & Telemetry
TARGET AUDIENCE
Security Architect Cybersecurity Engineer Chief Information Security Officer DevOps Engineer IT Manager Application Administrator Software Developer
EXTERNAL SOURCES
- Wikipedia - Credential stuffing
- OWASP - Definition and mitigations from OWASP
- Cloudflare - Vendor overview and mitigation advice
- NIST SP 800-63B - Digital identity guidelines for authentication
TOP QUESTIONS
How does Credential Stuffing differ from brute force attacks?
Credential stuffing uses known breached pairs; brute force guesses new combinations. The former exploits reuse, the latter tests password strength.
Category: Misunderstanding
What defenses stop Credential Stuffing?
Implement MFA, bot detection, rate limiting, IP reputation, device fingerprinting, and breached password screening.
Category: Management
What are the business risks of Credential Stuffing?
Account takeover, fraud, data breaches, and reputational damage. Regulatory penalties may apply for inadequate protection.
Category: Risk
What is a common mistake in Credential Stuffing mitigation?
Relying solely on CAPTCHAs without behavioral analytics or MFA, which attackers can bypass.
Category: Mistakes
How do password managers help against Credential Stuffing?
They encourage unique passwords per site, reducing reuse and the impact of breaches.
Category: Example
Why is monitoring for account takeover crucial?
Early detection of abnormal login patterns and device changes can prevent fraud and prevent lateral movement.
Category: Validation
Are breach corpuses used in Credential Stuffing public?
Attackers use leaked databases and dark web dumps; defenders can subscribe to breach alerts to respond quickly.
Category: Overview
Does MFA fully eliminate Credential Stuffing?
MFA greatly reduces risk but can be phished or bypassed in some flows. Layered controls remain essential.
Category: Opinion
Where to start learning about Credential Stuffing?
Use OWASP guidance, vendor blogs like Cloudflare and Microsoft, and NIST authentication standards for robust controls.
Category: Overview