On Tuesday 24 January 2023 at 11:34 UTC, a credential stuffing targeted a online casino customer in North America. The attack peaked at 283.5 million requests per second and lasted 184 minutes. Traffic originated from 2098 autonomous systems in 65 countries, predominantly a Mirai-derived IoT botnet.
| Vector | credential stuffing |
| Peak | 283.5 million requests per second |
| Duration | 184 min |
| Time to mitigation | 0.083 s |
| Attack traffic reaching origin | 0.037% |
| Legitimate traffic challenged | 0.74% |
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 519 within 31 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
No customer-visible impact. The on-call engineer was notified and acknowledged the incident from the dashboard.
Recommendations
- Enable authenticated origin pulls.
- Review allow-listed partner ranges quarterly.
- Enable log streaming to your SIEM for faster correlation.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
Do you publish the edge IP ranges in a machine-readable format?