← ClaudeAtlas

mobile-pentestlisted

Use when testing an Android or iOS mobile application for security issues — insecure data storage, weak crypto, insecure communication, authentication, platform misuse, reverse engineering / tampering resistance, and hardcoded secrets. Follows OWASP MASTG/MASVS and covers static, dynamic, and network testing. Authorized engagements only.
noahfranklin/gideon · ★ 2 · AI & Automation · score 70
Install: claude install-skill noahfranklin/gideon
# Mobile Application Penetration Testing Assessment of Android/iOS apps following the **OWASP Mobile Application Security Testing Guide (MASTG)** and verified against the **MASVS** controls. Combines static (the package), dynamic (running app), and network testing. ## 0. Authorization gate - [ ] Written authorization for the app + its backend/APIs. - [ ] Test devices/accounts provided; jailbreak/root allowed? - [ ] Backend testing scope (usually pair with `api-security-audit`). ## 1. Setup - Obtain the build (APK/AAB, IPA). Prepare instrumented device/emulator. - Intercept TLS via a proxy; handle certificate pinning (bypass only on your test build/device, in scope). ## 2. MASVS areas — test & fix ### Storage (MASVS-STORAGE) - Inspect local storage: shared prefs, SQLite, keystore/keychain usage, cached files, logs, backups. - **Look for:** PII/tokens/secrets stored in cleartext or world-readable locations. - **Fix:** platform keystore/keychain, no sensitive data in logs/backups. ### Crypto (MASVS-CRYPTO) - Hardcoded keys, weak algorithms, custom crypto, static IVs. - **Fix:** platform crypto APIs, keys in hardware-backed keystore. ### Auth & session (MASVS-AUTH) - Local auth bypass, insecure biometric gating, token handling, session invalidation. - **Fix:** enforce auth server-side; biometrics gate local secrets, not trust. ### Network (MASVS-NETWORK) - TLS validation, certificate pinning presence/quality, cleartext traffic. - **Fix:** TLS everywhere, pin certs, disabl