frida-mitm-capture

To capture HTTPS traffic with SSL pinning, you need to bypass certificate validation mechanisms using Frida scripts and forward decrypted traffic through a proxy. This skill automates injecting Frida hooks to bypass pinning and routing decrypted traffic to mitmproxy for analysis.

Yes, Frida can intercept and bypass OkHttp CertificatePinner by injecting custom scripts at runtime. This skill provides pre-built Frida scripts that automatically bypass OkHttp3 CertificatePinner, conscrypt TrustManagerImpl, and native libssl verification hooks.

Analyzing intercepted API requests requires parsing raw traffic data into a structured format. This skill forwards decrypted HTTPS traffic to mitmproxy and saves it as structured JSONL files, automatically identifying authentication headers and suspected encrypted fields.

Yes, bypassing SSL pinning for apps ignoring system proxy settings requires custom proxy routing configurations. This skill handles custom proxy routing to ensure traffic is forwarded to mitmproxy even when the app bypasses standard Android system proxy configurations.

Reverse engineering API signing algorithms requires capturing decrypted network traffic to inspect request parameters and headers. This skill automates HTTPS traffic capture with Frida SSL bypass and mitmproxy forwarding, outputting structured JSONL with encrypted field detection for analysis.

No, you do not need to manually write Frida scripts to intercept HTTPS traffic. This skill eliminates manual script configuration by providing an automated end-to-end workflow using pre-tested Frida scripts for SSL pinning bypass and mitmproxy traffic forwarding.