Think outside the server
summary
Three concrete risks: app mods strip ads and can harvest user data causing monetization loss and reputation damage; modified crypto wallets distributed via ads or Telegram steal funds while remaining indistinguishable to the server; game clients get cheated to poison player communities. Common defenses—name obfuscation, control‑flow scrambling, anti‑debugging—slow attackers but fail long term; the effective move is per‑build polymorphism that forces rework for each release. Measured median time to first runtime attack is 1 day.
AI-written summary · about
chapters (8)
- 0:00Introduction to client-side security
- 1:10Server vs client security models
- 5:06Scenario one app mods
- 10:05Scenario two crypto wallets
- 12:13Scenario three video game cheating
- 14:59Evaluating obfuscation techniques
- 18:09Polymorphic protection strategy
- 19:31Attack timeline and conclusion
related talks
33mHacking and protection of Mobile Apps and backend APIs
21mSecuring the Unseen: Advanced Threats, Best Practices & Challenges in Mobile App Security
21mWhen Attackers Go Mobile-First: What Developers Need to Know
40mBest practices for shielding mobile apps from emerging threats
24mModern Android App Security: Protecting Code, Keys, and Data
28mProtecting Mobile Games Against Hackers, Crackers & Copycatters
45mI just hacked your app!
36mI just hacked your app!