Android APK Penetration Testing
A comprehensive methodology for security testing Android applications.
Quick Start
- Static Analysis - Examine the APK without running it
- Dynamic Analysis - Test the running application
- Exploitation - Attempt to leverage findings
- Reporting - Document vulnerabilities
Static Analysis
Environment Setup
# Install essential tools
apktool
jadx
mobf
semgrep
# Optional: MobSF, Pithus, flutter-packer, rn-differ
Manifest Review
Check for:
- Debug mode enabled (
android:debuggable="true")
- Backup permissions (
android:allowBackup="true")
- Exported components (Activities, Services, Providers, Receivers)
- Network security config (
networkSecurityConfig XML)
- Intent filters and URL schemes
android:exported flag (mandatory on Android 12+)
- App Links / Deep Links (
android:autoVerify)
Critical checks:
- Unity Runtime: exported
UnityPlayerActivity/UnityPlayerGameActivity with unity CLI extras bridge
- Test
-xrsdk-pre-init-library <abs-path> for pre-init dlopen() RCE
- OEM ROM add-ons (OxygenOS/ColorOS/MIUI/OneUI) for extra exported ContentProviders
Code Analysis
Search for:
- Hardcoded credentials and API keys
- Insecure crypto algorithms (deprecated/weak)
- Sensitive data storage (internal/external)
- Firebase configuration and APIs
- Passwords, tokens, Bluetooth UUIDs
- Obfuscation presence (ProGuard, R8, etc.)
- Root detection, emulator detection, anti-tampering checks
WebView.addJavascriptInterface or loadData*() calls
- Play Integrity / SafetyNet / DeviceCheck implementations
Component Analysis
Test each component:
- Activities - especially exported ones
- Services - check for exposed services
- Content Providers - test for SQL injection, path traversal
- Broadcast Receivers - check for intent injection
- URL Schemes - verify intent handling
Library Analysis
- Check if all libraries compiled with PIE flag
- Scan third-party native libraries for known CVEs (libwebp CVE-2023-4863, libpng, etc.)
- Analyze cross-platform bundles (Flutter
libapp.so, React-Native JS bundles, Capacitor/Ionic assets)
- Use SEMgrep Mobile rules, Pithus, MobSF ≥ 3.9 AI-assisted scans
Dynamic Analysis
Environment Setup
- Online dynamic analysis environment
- Local VM or physical device
- ADB configured and working
- Proxy tool ready (Burp, mitmproxy, etc.)
Runtime Testing
Check for:
- Unintended data leakage (logging, copy/paste, crash logs)
- Confidential information in SQLite databases
- Exploitable exposed Activities (authorization bypass)
- Exploitable Content Providers (accessing/manipulating sensitive data)
- Exploitable exposed Services
- Exploitable Broadcast Receivers
- Clear text transmission / weak algorithms
- MitM possibilities
Traffic Inspection
- Intercept HTTP/HTTPS traffic
- Search for common Web vulnerabilities
- Check for Android Client Side Injections
- Verify certificate pinning
Runtime Hooking
Use Frida to:
- Obtain dynamic data from the application
- Bypass security checks
- Extract passwords and tokens
- Hook Play Integrity / SafetyNet
- Test runtime modifications
Modern tooling:
- Objection > 2.0
- Frida 17+ (Android 16 support, ART offset fixes)
- NowSecure-Tracer (2024)
- Dynamic system-wide tracing with
perfetto / simpleperf
Advanced Exploitation
- Tapjacking / Animation-driven attacks (TapTrap 2025) - even on Android 15+
- Overlay / SYSTEM_ALERT_WINDOW clickjacking
- Accessibility Service abuse for privilege escalation
adb backup / bmgr backupnow for app data dumping
- Binder-level LPEs (CVE-2023-20963, CVE-2023-20928)
- Play Integrity bypass:
Frida Gadget, MagiskIntegrityFix, Integrity-faker
- Recent Play Integrity Fix forks (≥17.x) with
playcurl
- ZygiskNext + PIF + ZygiskAssistant/TrickyStore combinations
OEM-Specific Testing
For OEM telephony/provider bugs (e.g., OxygenOS CVE-2025-10184):
- Attempt permission-less SMS read/send via
content CLI
- Test blind SQLi in
update() to exfiltrate rows
- Query:
content query --uri content://com.android.providers.telephony/ServiceNumberProvider without READ_SMS
Common Vulnerabilities Checklist
Authentication & Authorization
Data Protection
Network Security
Component Security
Runtime Security
Reporting
Document:
- Vulnerability description
- CVSS score
- Proof of concept
- Impact assessment
- Remediation recommendations
- References to CVEs where applicable
References
1---2name: android-apk-pentest3description: Android APK penetration testing methodology and checklist. Use this skill whenever analyzing Android applications for security vulnerabilities, performing mobile app security assessments, reverse engineering APKs, or conducting static/dynamic analysis of Android apps. Trigger for any Android security testing, APK analysis, mobile pentesting, or when investigating Android app vulnerabilities including exported components, insecure data storage, crypto issues, intent-based attacks, WebView exploits, or Play Integrity bypasses.4metadata:5 source: https://skillmd.com/skills/abelrguezr/android-apk-pentest6---78# Android APK Penetration Testing910A comprehensive methodology for security testing Android applications.1112## Quick Start13141. **Static Analysis** - Examine the APK without running it152. **Dynamic Analysis** - Test the running application163. **Exploitation** - Attempt to leverage findings174. **Reporting** - Document vulnerabilities1819## Static Analysis2021### Environment Setup2223```bash24# Install essential tools25apktool26jadx27mobf28semgrep29# Optional: MobSF, Pithus, flutter-packer, rn-differ30```3132### Manifest Review3334Check for:35- Debug mode enabled (`android:debuggable="true"`)36- Backup permissions (`android:allowBackup="true"`)37- Exported components (Activities, Services, Providers, Receivers)38- Network security config (`networkSecurityConfig` XML)39- Intent filters and URL schemes40- `android:exported` flag (mandatory on Android 12+)41- App Links / Deep Links (`android:autoVerify`)4243**Critical checks:**44- Unity Runtime: exported `UnityPlayerActivity`/`UnityPlayerGameActivity` with `unity` CLI extras bridge45- Test `-xrsdk-pre-init-library <abs-path>` for pre-init `dlopen()` RCE46- OEM ROM add-ons (OxygenOS/ColorOS/MIUI/OneUI) for extra exported ContentProviders4748### Code Analysis4950Search for:51- Hardcoded credentials and API keys52- Insecure crypto algorithms (deprecated/weak)53- Sensitive data storage (internal/external)54- Firebase configuration and APIs55- Passwords, tokens, Bluetooth UUIDs56- Obfuscation presence (ProGuard, R8, etc.)57- Root detection, emulator detection, anti-tampering checks58- `WebView.addJavascriptInterface` or `loadData*()` calls59- Play Integrity / SafetyNet / DeviceCheck implementations6061### Component Analysis6263Test each component:64- **Activities** - especially exported ones65- **Services** - check for exposed services66- **Content Providers** - test for SQL injection, path traversal67- **Broadcast Receivers** - check for intent injection68- **URL Schemes** - verify intent handling6970### Library Analysis7172- Check if all libraries compiled with PIE flag73- Scan third-party native libraries for known CVEs (libwebp CVE-2023-4863, libpng, etc.)74- Analyze cross-platform bundles (Flutter `libapp.so`, React-Native JS bundles, Capacitor/Ionic assets)75- Use SEMgrep Mobile rules, Pithus, MobSF ≥ 3.9 AI-assisted scans7677## Dynamic Analysis7879### Environment Setup8081- Online dynamic analysis environment82- Local VM or physical device83- ADB configured and working84- Proxy tool ready (Burp, mitmproxy, etc.)8586### Runtime Testing8788Check for:89- Unintended data leakage (logging, copy/paste, crash logs)90- Confidential information in SQLite databases91- Exploitable exposed Activities (authorization bypass)92- Exploitable Content Providers (accessing/manipulating sensitive data)93- Exploitable exposed Services94- Exploitable Broadcast Receivers95- Clear text transmission / weak algorithms96- MitM possibilities9798### Traffic Inspection99100- Intercept HTTP/HTTPS traffic101- Search for common Web vulnerabilities102- Check for Android Client Side Injections103- Verify certificate pinning104105### Runtime Hooking106107Use **Frida** to:108- Obtain dynamic data from the application109- Bypass security checks110- Extract passwords and tokens111- Hook Play Integrity / SafetyNet112- Test runtime modifications113114**Modern tooling:**115- Objection > 2.0116- Frida 17+ (Android 16 support, ART offset fixes)117- NowSecure-Tracer (2024)118- Dynamic system-wide tracing with `perfetto` / `simpleperf`119120### Advanced Exploitation121122- **Tapjacking / Animation-driven attacks** (TapTrap 2025) - even on Android 15+123- **Overlay / SYSTEM_ALERT_WINDOW clickjacking**124- **Accessibility Service abuse** for privilege escalation125- `adb backup` / `bmgr backupnow` for app data dumping126- **Binder-level LPEs** (CVE-2023-20963, CVE-2023-20928)127- Play Integrity bypass: `Frida Gadget`, `MagiskIntegrityFix`, `Integrity-faker`128- Recent Play Integrity Fix forks (≥17.x) with `playcurl`129- ZygiskNext + PIF + ZygiskAssistant/TrickyStore combinations130131### OEM-Specific Testing132133For OEM telephony/provider bugs (e.g., OxygenOS CVE-2025-10184):134- Attempt permission-less SMS read/send via `content` CLI135- Test blind SQLi in `update()` to exfiltrate rows136- Query: `content query --uri content://com.android.providers.telephony/ServiceNumberProvider` without `READ_SMS`137138## Common Vulnerabilities Checklist139140### Authentication & Authorization141- [ ] Weak authentication mechanisms142- [ ] Session management issues143- [ ] Authorization bypass in exported components144- [ ] Intent-based authorization bypass145146### Data Protection147- [ ] Insecure data storage (internal/external)148- [ ] Hardcoded credentials149- [ ] Weak or deprecated crypto150- [ ] Sensitive data in logs151- [ ] SQLite database exposure152153### Network Security154- [ ] Cleartext traffic permitted155- [ ] Certificate pinning bypass156- [ ] Weak TLS configuration157- [ ] API key exposure158159### Component Security160- [ ] Exported Activities without proper validation161- [ ] Exported Services without authentication162- [ ] Content Provider SQL injection163- [ ] Broadcast Receiver intent injection164- [ ] URL Scheme vulnerabilities165166### Runtime Security167- [ ] Root detection bypass168- [ ] Emulator detection bypass169- [ ] Anti-tampering bypass170- [ ] WebView JavaScript interface exposure171- [ ] Play Integrity / SafetyNet bypass172173## Reporting174175Document:176- Vulnerability description177- CVSS score178- Proof of concept179- Impact assessment180- Remediation recommendations181- References to CVEs where applicable182183## References184185- [CVE-2025-59489 – Arbitrary Code Execution in Unity Runtime](https://flatt.tech/research/posts/arbitrary-code-execution-in-unity-runtime/)186- [CVE-2025-10184 – OnePlus OxygenOS Telephony Provider Bypass](https://www.rapid7.com/blog/post/cve-2025-10184-oneplus-oxygenos-telephony-provider-permission-bypass-not-fixed/)187- [TapTrap Animation-Based Tapjacking Research](https://www.tomsguide.com/computing/online-security/this-new-android-attack-could-trick-you-into-compromising-your-own-phone-everything-you-need-to-know)188- [Hacktricks Android Pentesting](https://book.hacktricks.xyz/pentesting-mobile/android-app-pentesting)