Android app scan
Tenty reads the APK or AAB you upload and reports what anyone who downloads your app can find inside it.
What it is
An Android package is a zip file. Anyone with the app on their phone can copy it out and open it. Tenty reads the manifest, the strings of the compiled code, the resource strings and the JavaScript bundled for React Native or Capacitor.
Why it matters
Keys and settings in the package are public the day the app ships. The manifest decides how the app behaves on the phone:
- A debuggable build lets anyone with the phone attach a debugger and run code inside the app
- Plain HTTP traffic can be read and changed on a shared network
- Android backups copy the app's files, tokens included, off the phone
- An exported activity, service, receiver or provider takes calls from every other app on the phone
How Tenty checks it
Upload the file from the Android app card on the app page. The build takes its turn in the scan queue, and Tenty emails you once it is read, so you can close the page after the upload. Tenty reads the file once and deletes it. The same detectors that read your website's JavaScript run over the package, so live keys, Supabase and Firebase settings and AI calls show up the same way. The manifest checks follow the target API level of the build, since Android changed several defaults at API 28 and API 31.
Exported components are reported as possible, because deep links and share targets are exported on purpose. When the domain of the app is verified, Tenty also tests the Supabase and Firebase backends named in the package, the same way it tests the ones named on your website.
The Android app scan comes with the plans that include it. A finding missing from two uploads in a row is marked fixed.
Confirming the build is yours
The findings open once you confirm the build is yours. Download the proof file from the Android app card, sign it with the key you release the app with, and upload the signed file:
jarsigner -keystore release.jks tenty-proof.jar your-key-aliasTenty matches the key of the signed file to the key of the build and keeps it, so later builds signed with the same key open at once. A build signed with another key waits for a new proof. Upload a build you signed yourself: when Google Play signs the app for you, the copy downloaded from Play carries Google's key.
When the app is public on Google Play, Tenty can email a link to the developer address on its listing instead. The findings open once someone at that address confirms.
How to fix it
- Rotate any live key found in the package, then move the call that needs it to your server.
- Build releases with the release build type, which turns
android:debuggableoff. - Set
android:usesCleartextTraffic="false"or add a network security config that allows HTTPS only. - Set
android:allowBackup="false", or list what may leave the phone inandroid:dataExtractionRules. - Set
android:exported="false"on components other apps have no reason to call, and guard the rest withandroid:permission.
How to reproduce
unzip -l app.apk
unzip -p app.apk classes.dex | strings | grep -E 'sk_live_|AIza|supabase.co'
aapt2 dump xmltree app.apk --file AndroidManifest.xmlThe first command lists the files in the package. The second searches the compiled code for keys. The third prints the manifest, aapt2 ships with the Android SDK build tools.