On Friday 25 July 2025 at 14:42 UTC, a CLDAP reflection targeted a sports betting customer in Central Europe. The attack peaked at 168.0 Gbps and lasted 24 minutes. Traffic originated from 4153 autonomous systems in 28 countries, predominantly a Mirai-derived IoT botnet.
| Vector | CLDAP reflection |
| Peak | 168.0 Gbps |
| Duration | 24 min |
| Time to mitigation | 0.629 s |
| Attack traffic reaching origin | 0.059% |
| Legitimate traffic challenged | 0.47% |
Timeline
The attack was preceded by an extortion email received two days earlier. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 20 points of presence.
What the customer saw
No customer-visible impact. The on-call engineer was notified and acknowledged the incident from the dashboard.
Recommendations
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Enable log streaming to your SIEM for faster correlation.
- Add a dedicated rate limit for the targeted route.
Clear and practical, thanks.
How do you avoid challenging uptime monitors and partners?
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.
This matches what we see in iGaming around big matches.