Academy
TermAttack

Credential stuffing

Automatically trying username and password pairs leaked from one place on the same person’s accounts in other services.

Flow

  1. 1List obtained
  2. 2Tried automatically
  3. 3Valid ones used
Related families
—
MITRE ATT&CK
T1110.004 · Credential Stuffing
Sources
5 sources
01

Overview

The attack relies on password reuse: if the user uses the same password in more than one place, one leak opens the other accounts too. OWASP

It differs from password guessing; every pair tried belongs to a real person. This is why the success rate is much higher than a brute-force attack. MITRE ATT&CK

02

How it works

  1. 1

    List obtained

    Username–password pairs are taken from leak and log lists.

  2. 2

    Tried automatically

    Checker tools try the list on the target site through proxies. OWASP

  3. 3

    Valid ones used

    Opened accounts are sold or used directly for fraud. MITRE ATT&CK

03

Real-world examples

Password reuse and Snowflake

Mandiant stated that the attackers mostly obtained credentials through password reuse or through users downloading trojanized software. Google Cloud (Mandiant)

04

How to detect it

  • Login attempts to many accounts with few attempts each and many IP addresses. OWASP
05

What to do

  • Use multi-factor authentication. OWASP
  • Check new passwords against known leak lists. OWASP
  • Apply bot detection and rate limiting on the login page. OWASP
06

MITRE ATT&CK

07

Related terms

08

Sources

  1. 1Credential Stuffing (T1110.004) · MITRE ATT&CK
  2. 2Valid Accounts (T1078) · MITRE ATT&CK
  3. 3Credential stuffing · OWASP
  4. 4Credential Stuffing Prevention Cheat Sheet · OWASP
  5. 5UNC5537 targets Snowflake customer instances · Google Cloud (Mandiant), 2024