No Obfuscation / Symbol Stripping

← Code Quality & Build Config

no_obfuscation   EASY

Description

Ships with readable symbols; no ProGuard/R8/Dart obfuscation.

How it works

The build applies no obfuscation (no R8/ProGuard on Android or symbol stripping on iOS, no Flutter –obfuscate), so class and method names, URLs, and even key material are readable with standard reverse-engineering tools (jadx/strings on Android, class-dump/nm/strings on iOS), making reverse engineering trivial. This is a build-config property; the sample shows recoverable symbols.

How to exercise it. DVMA is the harness - open this module from the home index and tap the demo action. The screen ships the malicious input and simulates the attacker (e.g. the companion app, crafted intent, or scanned payload) in-process, and the evidence panel prints the proof. The Tools (optional) and Attack inputs below are only needed to reproduce the exploit end-to-end on a real device.

Exploit steps

1. Set up. Build DVMA with a flavor that enables the Code Quality & Build Config category (e.g. --dart-define-from-file=config/flavors/dev.json) and run on an emulator/simulator you control. The demo needs no external tooling; for the optional on-device reproduction the relevant tools are: strings, r2, Ghidra, JEB · Android: jadx, apktool · iOS: ipsw, nm, class-dump, Hopper, otool.
2. Locate the target. From the home index, open No Obfuscation / Symbol Stripping (no_obfuscation). The How it works section above describes this module’s specific weakness; the screen states the intended-secure behavior and exposes the vulnerable action.
3. Exploit. Statically inspect the shipped artifact (jadx, strings, nm, aapt dump badging) and confirm the build/quality weakness is present in the release binary.
4. Observe the evidence. Trigger the vulnerable action and read the evidence panel - it prints the concrete proof (leaked value, accepted replay, executed payload, or unauthorized result).
5. Contrast with the secure path. Run the module’s secure/hardened action (where provided) and confirm the same attack is rejected - this is what a correct implementation should do.
6. Map it back. Cross-reference the MASTG v2 test(s) MASTG-TEST-0051, MASTG-TEST-0093 for the canonical procedure and remediation.

Tools (optional)

• strings
• r2
• Ghidra
• JEB

Android

• jadx
• apktool

iOS

• ipsw
• nm
• class-dump
• Hopper
• otool