Summary
VaultDrop looks like a local Android anti-analysis and ContentProvider challenge, but the winning path is the hardcoded HS256 JWT secret inside the native library. After extracting that secret from libvault_crypto.so, a normal user can sign a forged JWT with role=admin, enumerate endpoints with the valid admin token, and reach the hidden /api/admin/flag route. The misleading part is that /api/files ignores the elevated role claim and keeps returning the same user file list, so the real privilege escalation only becomes visible on the hidden admin endpoint.
Solution
The challenge can be solved in 5 steps:
Step 1 - Reverse the APK and locate the trust boundary
The APK performs several anti-analysis checks through SecurityGuard.enforce() and nativeEnforceIntegrity(), but the important part is the VaultCrypto interface. The native library exports getAppJwtSecret(), decryptConfig(), getDbPassphrase(), and nativeEnforceIntegrity(). That immediately suggests that authentication material is stored in client-side native code.
Step 2 - Extract the JWT signing secret from libvault_crypto.so
Reversing the native library reveals the static HS256 signing secret used by the app:
4536ecd6d1c79c770306392bc7e20b0045437682694d3db5ab77220b8b5d76db
Because the backend accepts tokens signed with this shared secret, anyone who extracts it can mint valid JWTs offline without interacting with the normal authentication flow.
Step 3 - Register a normal user and forge an admin token
Register any regular account first so there is a valid subject value already known to the backend. Then generate a new JWT that keeps sub equal to that real username but changes role to admin, signs it with HS256, and sets fresh iat and exp values. Testing showed that forged tokens were accepted by the server as long as the sub matched an existing user.
Step 4 - Treat /api/files as a decoy and enumerate endpoints
The first instinct is to call /api/files with the forged token, but that endpoint keeps returning the same two files and ignores extra claims such as scope or permissions. The real progress came from broader endpoint discovery with the forged admin token. That process identified a hidden admin-only route at /api/admin/flag.
Step 5 - Query the hidden flag endpoint with the forged JWT
Send a GET request to /api/admin/flag with Authorization: Bearer <forged_admin_token>. The server accepts the JWT, recognizes the elevated role on the admin endpoint, and returns the flag in JSON together with the message "The vault has been breached. Well played."