Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/mobile-cert-pinning-bypassMobile, firmware and hardware

mobile-cert-pinning-bypass

⁨Bypass TLS certificate pinning so you can proxy a mobile app's traffic. Load when a proxy shows no/broken traffic, you see SSL handshake failures in logs, OkHttp CertificatePinner, TrustKit, or "the app won't connect through Burp". Android/iOS.⁩

v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/mobile-cert-pinning-bypass

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
o4bQNINmSR…iHoO6bBA==The CLI checks the SHA-256 and the signature before it writes a file.
Package692e7ffe…3dd93ed7
692e7ffe884c…48693dd93ed71 file · ⁦1.2 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/mobile/mobile-cert-pinning-bypass@ee0e0c5

When it applies

The app pins its server cert, so a normal MITM proxy (Burp/mitmproxy) can't decrypt its traffic — you get handshake errors and empty history. You need to test the backend, so the pin has to go.

Why it works

Pinning is enforced in the client you control. At runtime you can replace/neutralize the verification routine; statically you can patch it out. Either way the app then trusts your proxy's CA.

Method

  1. Install your CA first: add Burp/mitmproxy CA to the device (Android 7+ needs it as a system cert, or use a network_security_config on a repackaged app).
  2. Runtime (fastest): objection -g <pkg> explore then android sslpinning disable (iOS: ios sslpinning disable), or a Frida script (frida-multiple-unpinning).
  3. Static patch (when Frida is blocked): apktool d, remove/patch the CertificatePinner / TrustManager checks or swap network_security_config to trust user CAs, rebuild + resign (apktool b, uber-apk-signer).
  4. Confirm: traffic now appears decrypted in the proxy; proceed to backend testing.

Gotchas

  • No traffic at all (not just pinning) can mean the app uses a non-HTTP protocol or a VPN — check.
  • Some apps double-pin or detect Frida/root — combine root-detection bypass, or use static patching.
  • iOS on a non-jailbroken device needs a repackaged/sideloaded app or a jailbroken test device.

Verify success

The proxy shows plaintext requests/responses from the app; you can now replay/modify them.

References

OWASP MASTG (network); objection & frida-multiple-unpinning; TrustKit/OkHttp docs.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5692e7ffeSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login