Demonstration of Static & RASP Framework

This release provides three distinct APKs to demonstrate and validate the multi-layered security framework:

1. Messanger_NO.apk (Unprotected Debug Build)

This is the standard, unprotected debug build. All custom security features are DISABLED.

• RASP: The app will run normally on emulators and will not detect debuggers or root.
• Obfuscation: Code is not obfuscated or minified.
• Purpose: This is the "before" control. Use JADX on this file to see the original, readable source code.

2. Messanger_YES.apk (Protected Release Build - Unsigned)

This is the fully protected aggressiveRelease build, but it has not been signed.

• Obfuscation: The code is fully minified, obfuscated (e.g., a.b.c), and strings are encrypted.
• Purpose: This file is for static analysis only. You can decompile this with JADX to see the fully obfuscated code and compare it to Messanger_NO.apk.
• Note: This APK will not install on a standard device because it is unsigned.

3. Messanger_Signed_yes.apk (Protected Release Build - Signed)

This is the final, runnable production build, signed with the official release key. It has all Obfuscation and RASP features ENABLED.

• RASP: The app will actively detect threats. It will terminate immediately if run on an emulator, a rooted device, or if a debugger is attached.
• Obfuscation: The code is identical to Messanger_YES.apk (fully obfuscated).
• Purpose: This is the final, testable "after" version. Use this file to test the RASP module's runtime checks (anti-debug, anti-root, anti-emulator, and anti-tampering).