In recent years, decompilers have reached a maturity level that allows recovering source code from mobile app binaries with ease. Obfuscation has become a well established preventive measure developers use against static reverse engineering attempts. There are several ways to implement obfuscation, but various obfuscation solutions differ in several things: Ease of use (e.g., specialized compilers and post-build tools), Performance (i.e., performance penalty, if any) and the reference threat level.
Since eventually all defenses can be broken, the quality of a good defense is measured by the amount of work, expertise and time needed to break the defense.
This Knowledge Base article provides step-by-step instructions for using Appdome to add code packing to Android mobile apps. This protects any Android mobile app from static reverse engineering attempts.
We hope you find this knowledge base useful and enjoy using Appdome!
About No-Code Android APPCode Packer on Appdome
Appdome is a no-code mobile integration platform as a service (iPaaS). Appdome allows users to add a wide variety of features, SDKs and APIs to Android and iOS applications. Using a simple ‘click to add’ user interface, anyone can easily add Appdome’s APPCode Packer and other code obfuscation methods to any mobile application – in seconds, no-code or coding required.
Using Appdome, there are no development or coding prerequisites. For example, there are no SDK, library, or plug-ins to implement. The Appdome technology adds APPCode Packer and relevant standards, frameworks and more to the app automatically, with no manual development work at all.
Appdome’s APPCode Packer is a security feature that encrypts the mobile app’s compiled Java code and decrypts it at run-time. Appdome’s APPCode Packer makes reverse engineering an arduous task while preserving the functionality and performance of the original app. Appdome’s APPCode Packer is compatible with mobile apps built in any development environment including Native Android apps, hybrid apps, and non-native apps built-in Xamarin, Cordova, and React Native, Ionic and more. This streamlines implementations, cuts development work, and ensures a guaranteed and consistent integration of Appdome’s APPCode Packer to any mobile app.
APPCode Packer in Android Mobile Apps
In Android, compiled Java/Kotlin code resides in
classes.dex files (see structure of Android applications). The common toolbox to reverse engineer DEX files contains Disassemblers such as baksmali and dex2jar and decompilers such as jadx and jdgui. The purpose of Appdome’s APPCode Packer is to make these tools ineffective and even unusable. To do this, Appdome encrypts all DEX files not needed for app initialization, making it impossible for disassemblers to find the original code. At run-time, Appdome’s code will decrypt the encrypted DEX files and allow the app to continue working as usual.
This obfuscation technique provides the following benefits:
- Trying to use offline reversing techniques on the application will fail as most classes will not be found in the APK or in the AAB.
- Decryption overhead is only incurred during the app’s first run, and even then has minimal impact.
- Since the DEX files are encrypted, they are protected by Appdome’s Anti-Tampering.
- In addition, any attempt to force this information out of the application using run-time methods will be met with Appdome’s Anti-Debugging
This feature is complementary to Appdome’s Control-Flow Relocation and may be used together to further the app’s Java code reverse-engineering protection.
The Android App Bundle lets you more easily deliver a great experience in smaller app size, by creating “splits”, allowing the play store the ability to tailor fit the app to the phone it’s being installed on, Downloading only the relevant resources.
If your application was developed using a non-native framework such as React-Native, Cordova or Xamarin, you might want to check out Non-Native Code Obfuscation.
If, on the other hand, your application has more native code in it, we recommend you check out Binary Code Obfuscation.
APPCode Packer Caveat
Since the app still requires certain classes for its initial startup, specific classes mentioned by the following tags in the app’s manifest inside the “application” tag will not be encrypted:
- android: appComponentFactory
- android: name