android-pentestlisted
Install: claude install-skill AnandJogawade/Zazy-Pentest-Plugin-for-Claude
# Android Penetration Testing
Test the app (static + dynamic), its local data, its IPC surface, and its backend. Align to OWASP MASVS; use MASTG techniques. Most high-impact findings are insecure storage, broken IPC/exported components, weak crypto, and backend authorization.
## Trigger phrases
`android, apk, mobile app, frida, objection, mobsf, smali, deep link, webview, certificate pinning, root detection, keystore`
## Toolchain (WSL/Kali or host)
`apktool`, `jadx`/`jadx-gui`, `dex2jar`, `MobSF` (static+dynamic), `frida`/`objection`, `adb`, `drozer`, `nuclei`, Burp with device proxy, an emulator (Genymotion/AVD) or rooted device.
## 1. Acquire & inventory
- Obtain the APK (from device via `adb pull`, or provided). Split APKs: merge with `apkeditor`/bundletool.
- `MobSF` for a fast baseline. Then manual: `apktool d app.apk` (resources/manifest/smali), `jadx` (Java source).
## 2. Static analysis
- **Manifest:** `android:debuggable`, `allowBackup`, `usesCleartextTraffic`, `minSdk` (old = more exploitable), exported `activity`/`service`/`receiver`/`provider` (no permission), custom permissions, deep-link `intent-filter` schemes/hosts, `networkSecurityConfig`.
- **Secrets:** hardcoded API keys, tokens, endpoints, crypto keys, Firebase URLs, cloud creds in `strings.xml`, `BuildConfig`, resources, native libs (`strings` on `.so`). Check for exposed Firebase (`<proj>.firebaseio.com/.json`), open S3/GCS.
- **Crypto & logic:** weak algorithms (ECB, hardcoded IV/keys), custom cr