android-apk-recon-staticlisted
Install: claude install-skill AnandJogawade/Zazy-Pentest-Plugin-for-Claude
# Android APK Recon & Static Analysis
Acquire the APK (merging splits), decompile it, and map the code so later skills know where to look. First step of every Android test.
## Trigger phrases
`apk, pull apk, split apk, apkeditor, apktool, jadx, dex2jar, apkid, decompile, smali, android static analysis, mobsf baseline`
## Method
1. **Locate & pull** the package:
- `adb shell pm list packages | grep <keyword>`
- `adb shell pm path <package>` — lists base + split paths.
- `adb pull /data/app/.../base.apk ./`
2. **Merge split/App-Bundle APKs** (standalone base often won't install / misses resources):
- `adb shell pm path <package> | cut -d ':' -f 1 | xargs -n1 -I{} adb pull {} splits/`
- `java -jar APKEditor.jar m -i splits/ -o merged.apk`
- `java -jar uber-apk-signer.jar -a merged.apk --allowResign -o merged_signed`
3. **Baseline with MobSF** (automated static) for a fast overview, then go manual.
4. **Decompile:**
- `apktool d app.apk -o app_src` — smali + decoded manifest + resources.
- `jadx -d app_java app.apk` (or `jadx-gui app.apk` interactive) — Java.
- `d2j-dex2jar app.apk -o app.jar && jd-gui app.jar` — alternate Java path when jadx fails.
5. **Fingerprint packing/obfuscation:** `apkid app.apk` — flags packers, obfuscators, anti-VM/anti-debug (dictates whether you need `android-native-lib-analysis` / `android-root-antidebug-bypass`).
6. **Map the attack surface** — grep decompiled code for entry points and dangerous APIs:
- `grep -rniE "