A modular, black-box obfuscation tool for Android apps (APK/AAB) that works without source code.
Obfuscapk is an automatic obfuscation tool for Android applications that operates in a black-box manner. It takes compiled APK or Android App Bundle (AAB) files, decompiles them, applies a configurable set of obfuscation techniques to the smali code and resources, and rebuilds a protected app. The tool helps developers safeguard their apps against reverse engineering and tampering without needing access to the original source code.
Android developers and security researchers who need to protect their apps from reverse engineering, or who want to test obfuscation techniques against analysis tools. It's also suitable for those studying mobile app security and obfuscation methods.
Obfuscapk offers a modular, extensible, and automated approach to Android obfuscation that works without source code. Unlike manual or proprietary solutions, it's open-source, supports both APK and AAB formats, and allows users to chain multiple obfuscation techniques in a customizable pipeline.
An automatic obfuscation tool for Android apps that works in a black-box fashion, supports advanced obfuscation features and has a modular architecture easily extensible with new techniques
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Works directly on compiled APK or AAB files without needing source code, using Apktool for decompilation and rebuilding, as highlighted in the description.
Built on Yapsy plugin system, making it easy to extend with new obfuscators by adding source code and metadata, as detailed in the architecture section.
Includes a wide range of obfuscators like encryption, reflection, and code reordering, listed with descriptions in the README's obfuscators section.
Can handle both traditional APKs and Android App Bundles, though AAB support relies on BundleDecompiler and has platform limitations.
The project is explicitly marked as archived, meaning no bug fixes, security updates, or compatibility with future Android SDKs or tools.
Requires manual installation of external tools like apktool, BundleDecompiler, Java, and Python dependencies, with environment variable configurations, increasing setup time and risk of errors.
AAB obfuscation is not supported on Windows due to BundleDecompiler's incompatibility, as noted in the README, restricting cross-platform usability.
Aggressive obfuscation can introduce runtime errors or crashes, requiring thorough testing and use of ignore options, with no guarantees from the unmaintained codebase.