apk-redteam-pipeline

Automate Android APK security auditing by decompiling applications with jadx and scanning for over 60 high-signal secret patterns, including cloud keys, JWTs, and internal API endpoints. This pipeline handles acquisition, static analysis, and runtime instrumentation to identify insecure component configurations.

Yes, you can use Frida and objection to bypass certificate pinning and trace API calls in real-time. The pipeline provides runtime instrumentation templates that integrate with static analysis results to facilitate dynamic testing of Android applications.

Fetch Android APKs from the Play Store, APKPure, and APKMirror using package IDs or brand names. The automated acquisition feature retrieves target application files directly, providing the necessary inputs for decompilation and subsequent vulnerability discovery.

Yes, you need jadx for automated decompilation and static analysis, alongside frida-tools, objection, and mitmproxy for runtime instrumentation and traffic interception. These dependencies are required to execute the integrated end-to-end security assessment workflow.

Automated decompilation relies on jadx to translate APKs into readable source, meaning heavily obfuscated code can obscure hardcoded secrets and insecure component configurations. Runtime instrumentation with Frida is necessary to trace obfuscated API calls dynamically when static greps fail.

Automated recon for vulnerability discovery is limited by its reliance on static pattern matching, which may miss complex logic flaws or dynamically loaded payloads. It identifies hardcoded secrets and insecure configurations but requires manual runtime instrumentation to confirm exploitable vulnerabilities.