Obfuscation in Mobile Apps
summary
Obfuscation reduces easy reverse engineering by adding runtime string decryption, fake execution paths and expanded math so static decompilation becomes costly; tradeoffs are bigger binaries, slower performance and harder production debugging. Examples: JavaScript and React Native bundle remain trivial to extract, JVM dex yields readable smali via APKTool, while NDK C/C++ compiles to assembly that needs professional tools like Hopper disassembler or IDA and is much harder to recover. An open project called OMLL / opencator is being developed toward Q3 production readiness.
AI-written summary · about
chapters (8)
- 0:00Introduction to obfuscation
- 1:50Why obfuscate mobile apps
- 3:18Impact of obfuscation techniques
- 5:22Language choice affects obfuscation
- 8:44JavaScript vs JVM vs C code
- 10:46Flutter and Dart for protection
- 12:14Key takeaways and recommendations
- 13:20OMLL project announcement
related talks
46mDiscovering and Mastering Obfuscation on Android
45mReverse engineering mobile apps: how, why, and what now?
36mMaster the Art of Code Obfuscation from Simple to Advanced
45mGoing Beyond Obfuscation: Advanced Techniques for Protecting Android Apps
36mPractical obfuscation guide
47mAttacking Android Applications
33mShielding Your Android App from Attackers
29mEndoscope: Unpacking Android Apps with VM-Based Obfuscation