← ClaudeAtlas

android-insecure-storagelisted

Find sensitive data stored insecurely on-device — plaintext credentials, tokens, PII in shared_prefs, SQLite databases, files, external storage, and cache — via run-as/root, sqlite3, strings, and objection. Tier 1. Use after exercising app features. Aligns to OWASP MASTG MASVS-STORAGE (MASTG-TEST-0001).
AnandJogawade/Zazy-Pentest-Plugin-for-Claude · ★ 26 · AI & Automation · score 82
Install: claude install-skill AnandJogawade/Zazy-Pentest-Plugin-for-Claude
# Android Insecure Data Storage Trigger app features, then inspect every on-device storage location for plaintext secrets, tokens, and PII. ## Trigger phrases `insecure storage, shared_prefs, sqlite, databases, external storage, sdcard, cache, run-as, objection explore, plaintext token on device` ## Method 1. **Exercise the app first** — log in, store a card, save notes, etc., so secrets are actually written. 2. **Enumerate storage locations:** - `/data/data/<package>/shared_prefs/`, `/databases/`, `/files/`, `/cache/` - `/sdcard/Android/data/<package>/` and `/sdcard/` (external — world-readable pre-scoped-storage). 3. **Inspect (root or debuggable app via `run-as`):** - `adb shell run-as <package> cat shared_prefs/*.xml` - `adb shell run-as <package> ls databases/` - `adb pull /data/data/<package>/databases/app.db && sqlite3 app.db ".tables" ".dump"` - `strings` over files/cache for residual secrets. 4. **objection** (no manual rooting of paths): ``` objection -g <package> explore android > env # dumps app dirs android > sqlite connect <db> ``` 5. **Check insecure modes** — `MODE_WORLD_READABLE`/`MODE_WORLD_WRITABLE` (grep decompiled code for `openFileOutput(... MODE_WORLD`), and sensitive residue in external storage/cache. ## Modern / rare techniques - **EncryptedSharedPreferences / SQLCipher key recovery** — if "encrypted" storage is used but the key is derived in-app or keystore auth isn't bound, dump the key at runtime