apk-recon

Detect secrets, insecure storage, weak crypto, and misconfigurations in Android APKs.

48|27|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/abisheikM1/Tribunal --skill apk-recon-abisheikm1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apk-recon
Source: https://github.com/abisheikM1/Tribunal/tree/main/legacy-harness/skills/apk-recon
Command: npx skills add https://github.com/abisheikM1/Tribunal --skill apk-recon-abisheikm1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Android apps often ship with hardcoded API keys, insecure storage settings, weak cryptography, and risky manifest flags that are tedious to hunt manually across decompiled code. This Skill runs a broad first-pass recon sweep over an APK to surface those exposure leads and prioritize which ones deserve deeper investigation. ## Core Features & Use Cases - Manifest & secrets correlation: Combines parse_manifest.py and scan_secrets.py output into one prioritized summary via recon_summary.py, bucketing findings into pivot, verify, and high lanes with severities. - Weak crypto and TLS detection: Provides grep passes for ECB/DES ciphers, static IVs, MD5/SHA-1, insecure randomness, and trust-all TrustManagers, plus Network Security Config review. - Dynamic verification guidance: Supplies human-run adb commands for adb backup extraction, run-as sandbox inspection, logcat secret hunting, and MediaProjection/lockscreen notification checks. - Use Case: You receive an authorized Android app to pentest. Run the recon pass to immediately surface a hardcoded Firebase URL and an allowBackup flag, then hand the live endpoint to API testing and verify the backup actually contains session tokens before reporting. ## Quick Start Ask the agent to run a first-pass secrets and configuration recon on the APK in the apk/ directory and summarize the prioritized findings.

Frequently Asked Questions about apk-recon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find hardcoded secrets and API keys in an Android APK?

Run scan_secrets.py with the APK path to generate secrets.json with regex hits for AWS keys, Google API keys, Firebase URLs, JWTs, and private keys, then run recon_summary.py to bucket them into prioritized lanes. apkleaks runs automatically inside the scan for endpoint extraction.

How do I check if an Android app is debuggable or allows backup?

Run parse_manifest.py to extract the debuggable, allowBackup, and usesCleartextTraffic flags into manifest.json, then recon_summary.py flags each risky setting with a severity and a verification command like adb backup or run-as.

Does this tool automatically exploit the vulnerabilities it finds?

No. It is a detection and methodology aid only: it prints findings and the adb or grep commands a human should review and run on an authorized device. It never issues network requests or attacks anything, and cloud credential validation requires explicit program authorization.

What tools are required to run Android APK recon?

You need Python 3.10+, Java with apktool and jadx for decompilation, and adb for dynamic checks on an authorized device. The correlator script uses only the Python standard library and degrades gracefully if optional tools are missing.

Why are findings like debuggable or missing certificate pinning marked low severity?

Client-side flags like debuggable, cleartext, or missing pinning are usually informational alone because they enable testing more than they harm users. Severity rises only when you verify actual sensitive data exposure or chain the finding into server-side impact.