Course contentsShow
← Security
Lesson 699 of 3,05215. Web Security - Authentication and SessionsFree lesson

Password Spraying Techniques

Learn how attackers use common passwords against many accounts to avoid lockouts and detection mechanisms.

Password Spraying Techniques

What you'll learn: How attackers avoid account lockouts by testing common passwords against many accounts instead of hammering one account with many passwords.

What is Password Spraying?

Password spraying is a low-and-slow brute force attack where adversaries reverse the traditional approach. Instead of trying thousands of passwords against one account (which triggers lockout mechanisms), they try one common password against thousands of accounts.

How Password Spraying Works

Attackers exploit two realities:

  1. Organizations have weak account lockout policies (or none at all for authentication endpoints)
  2. People use common, predictable passwords like "Password123!", "Summer2024!", or "CompanyName1"

The attack pattern looks like this:

Try "Password1" against:
  - alice@company.com
  - bob@company.com
  - carol@company.com
  ...
  (repeat for 1000s of accounts)

Wait 30+ minutes (to reset any rate limits)

Try "Welcome123!" against all accounts again

Why This Evades Detection

Traditional account lockout policies trigger after 5-10 failed attempts per account. Password spraying only hits each account once per round, staying under the threshold. Security monitoring systems looking for rapid-fire attempts against single accounts miss this distributed pattern.

Real-World Impact

Combined with credential stuffing (using breach databases), password spraying becomes devastatingly effective. Attackers often target authentication endpoints without CAPTCHA protection, federation services, or VPN login pages—anywhere they can enumerate valid usernames and test credentials quietly.

Key Takeaway: Password spraying defeats lockout mechanisms by distributing failed login attempts across many accounts with common passwords, making it essential to implement rate limiting at the IP and network level, not just per-account lockout policies.