I have no idea what my app is doing ¯\_(ツ)_/¯ - Protecting your application from unintended side eff
summary
Practical checklist for preventing unintended app behavior: inspect real HTTP traffic with Charles proxy or on-device Chucker; review the merged Android manifest to find permissions added by libraries; and lock or control Gradle dependencies—use dependency locking (run with -Dwrite-locks), constraints/force or transitive=false, and be aware Gradle’s lexicographic version resolution can cause conflicts. Also recommended: scan with OWASP dependency-check and be cautious of malicious packages historically hosted on JCenter.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:10Big codebase onboarding
- 6:09Detecting app behavior
- 11:21Managing dependencies
- 16:44Dependency version resolution
- 22:06Dependency security risks
- 27:46Malicious package attacks
- 30:12Vulnerability checks
- 30:53Summary
related talks
39mI have no idea what my app is doing
38mAdvanced Techniques for Protecting Android Apps
38mBreak your App before Someone Else Does
47mDefending Your Users
45mGoing Beyond Obfuscation: Advanced Techniques for Protecting Android Apps
39mAndroid App Security Fundamentals
45mBreak your app before someone else does
01h 07mHow to attack (and secure) an Android app: an introduction