Break your app before someone else does
summary
Shows how to extract an APK with ADB pull, inspect permissions and manifest, and use apktool rebuild to add or remove assets then re‑sign with a custom keystore so the APK still installs. Demonstrates rapid checks with Google Play pre‑launch report (about ten devices, five minutes of automated taps) and live traffic manipulation with Charles proxy. Mentions ClassyShark and AndroidGuard for class and permission browsing and recommends tampering detection, network security config, and QA scripts to catch real‑world failures.
AI-written summary · about
chapters (21)
- 0:00Introduction to app security
- 1:25Static analysis and lint tools
- 3:51Testing and QA importance
- 6:19Role of QA teams in testing
- 8:29Pre-launch reports and Firebase
- 10:59Crash reporting with Fabric
- 12:49Penetration testing necessity
- 14:36Extracting APKs from devices
- 17:49Tools for APK inspection
- 21:21Modifying APKs with basic tools
- 25:18APKTool for reverse engineering
- 29:15Changing APK assets and resources
- 31:25Tampering detection techniques
- 33:11ClassyShark for APK analysis
- 34:38Ease of reverse engineering
- 36:01AndroidGuard for malware analysis
- 36:42Charles Proxy for network testing
- 38:07HTTPS and security basics
- 40:15API response handling
- 41:41Protecting user data
- 42:02Conclusion and call to action
related talks
45mBreak your app before someone else does
38mBreak your App before Someone Else Does
38mReverse Engineering is not just for hackers
44mAuditing Your APKs Like a Black Hat Hacker
45mReverse engineering mobile apps: how, why, and what now?
47mAttacking Android Applications
30mA day in the life of a mobile reverse engineer
42mAttack & Defend Mobile Apps