Password Spraying

Password Spraying Overview

At its core, password spraying is about doing one thing well inside your authentication project. Once you understand the pattern, you can apply it consistently across features and teams.

Good password spraying pays off across the whole codebase: fewer surprises, easier testing, and smoother onboarding. The snippet below is a solid starting point.

import rateLimit from 'express-rate-limit';

const loginLimiter = rateLimit({
  windowMs: 15 * 60 * 1000,
  max: 5,
  message: 'Too many login attempts, try again later',
});

app.post('/login', loginLimiter, loginHandler);

Rate limiting login attempts is a first line of defence against brute-force attacks.

Password Spraying Example

// verify the caller on every protected request
function authenticate(req, res, next) {
  const token = req.headers.authorization?.replace('Bearer ', '');
  req.user = verifyToken(token); // throws if invalid
  next();
}

• Start from a minimal Password Spraying example and grow it only as needed.
• Keep configuration explicit so Password Spraying behaves the same in every environment.
• Name things clearly so teammates understand your Password Spraying at a glance.
• Add tests around Password Spraying early to lock in expected behaviour.

Authentication Cheatsheet

Quick authentication reference related to password spraying.

How Password Spraying Works

Password Spraying is part of proving who a user is and what they are allowed to do. Authentication verifies identity, while authorization decides access — and password spraying plays a specific role in that flow.

Rate limiting login attempts is a first line of defence against brute-force attacks.

• Never store or log plain-text passwords or secrets.
• Prefer short-lived tokens with refresh over long-lived ones.
• Always send credentials over HTTPS.
• Fail closed: deny access when anything is uncertain.

Security Guidance for Password Spraying

Security is the whole point of password spraying. Small mistakes — weak hashing, tokens in localStorage, missing rate limits — are exactly what attackers look for, so follow proven defaults.

Common Mistakes

• Skipping error handling and edge cases when wiring up password spraying.
• Leaving password spraying untested, so regressions slip into production.
• Over-engineering password spraying before you actually need the extra flexibility.
• Ignoring documentation, which makes password spraying hard for the next developer to change.

Key Takeaways

• Password Spraying is a core part of working effectively with authentication.
• Start small and keep password spraying focused on a single responsibility.
• Apply consistent patterns so password spraying scales across your project.
• Test and document password spraying to keep it maintainable over time.