On Thursday 9 June 2022 at 19:09 UTC, a login endpoint flood targeted a fashion retail customer in Latin America. The attack peaked at 865.9 million requests per second and lasted 42 minutes. Traffic originated from 4132 autonomous systems in 88 countries, predominantly mobile carrier ranges.
| Vector | login endpoint flood |
| Peak | 865.9 million requests per second |
| Duration | 42 min |
| Time to mitigation | 0.492 s |
| Attack traffic reaching origin | 0.007% |
| Legitimate traffic challenged | 0.28% |
Timeline
The attack was preceded by a ransom note demanding payment in Monero. Request rates on the targeted routes exceeded their hourly baseline by a factor of 286 within 17 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
A brief increase in p99 latency of 40 ms during the first minute, then normal service.
Recommendations
- Enable log streaming to your SIEM for faster correlation.
- Review allow-listed partner ranges quarterly.
- Enable authenticated origin pulls.
How do you avoid challenging uptime monitors and partners?
Thanks! Yes — the risk score and its components are included in every log record.
Could you share the dataset behind the percentages?