On Thursday 27 June 2024 at 12:15 UTC, a credential stuffing targeted a crypto exchange customer in Central Europe. The attack peaked at 213.5 million requests per second and lasted 86 minutes. Traffic originated from 1261 autonomous systems in 100 countries, predominantly a rented booter service.
| Vector | credential stuffing |
| Peak | 213.5 million requests per second |
| Duration | 86 min |
| Time to mitigation | 0.327 s |
| Attack traffic reaching origin | 0.049% |
| Legitimate traffic challenged | 0.40% |
Timeline
The attack was preceded by a competitor’s product launch. Request rates on the targeted routes exceeded their hourly baseline by a factor of 396 within 12 seconds. The risk score of participating clients crossed the challenge threshold automatically and proof-of-work difficulty rose with origin load.
What the customer saw
Checkout conversion was unchanged compared with the same hour of the previous week.
Recommendations
- Add a dedicated rate limit for the targeted route.
- Keep origin IPs out of public DNS history.
- Review allow-listed partner ranges quarterly.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?