No Rate Limiting. 150 Million Spotify Accounts Targeted in One Night.
In 2020, a credential stuffing attack hit Spotify. Attackers had a database of 380 million username and password pairs from previous breaches across other sites. They wrote a script to try each one against Spotify's login endpoint — automatically, thousands of requests per second. Because Spotify had no effective rate limiting on their API at the time, the script ran unhindered all night.
By morning, over 300,000 accounts had been successfully taken over. Users woke up to find their playlists deleted, their email changed, and their subscription being used from a different country. The attackers did not hack Spotify at all — they just tried passwords that worked somewhere else.
This is exactly what you will do in the Chirper lab — write a loop, try passwords, find the one that works. The only difference is you have permission to do it there.
But Yahoo is just the most visible example of a systemic problem. Authentication failures — weak passwords, no rate limiting, poor session management — are behind the majority of account takeovers that happen every single day.
How attackers get in without hacking
Most account takeovers do not involve a sophisticated attack. They follow one of three simple paths:
An attacker uses leaked passwords from the LinkedIn breach to log into Netflix accounts. What is this called?
What percentage of data breaches involve stolen or weak credentials according to the Verizon DBIR?