Your App is a Giant DDOS Botnet
summary
An app can amplify retries into a global outage: millions of devices repeatedly resending failed analytics created exponential log storms that looked like a DDoS. The team builds an in-app network monitor using OKHTTP interceptors, persists state with Realm, and accepts a remote 555 error code to instruct devices to back off with randomized timers. The system flags gradual data growth, prevented a release panic, and diagnosed one intern’s runaway background traffic.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 3:15The accidental botnet incident
- 7:44Systematic mobile traffic management
- 11:10Shutting off bad network traffic
- 18:39Monitoring network traffic trends
- 25:24Open source plans and key takeaways
- 26:46Q&A session
related talks
21mFortify the Fort: Think outside the security
07mSuccess Breeds Panic: shares the story of his first security incident
42mWarding against the Dark Arts: Crafting a Defense Strategy against Botnet DDoS
52mKnock Knock: Understanding Who is Using Your Web Applications
52mInvestigating DDOS - Architecture Actors and Attribution
45mI just hacked your app!
52mNot all attacks are malicious: DDoS from outside and within
25mElevating Android App Resilience: Incident Management Strategies