| name | intercepting-mobile-traffic-with-burpsuite |
| description | Intercepts and analyzes HTTP/HTTPS traffic from mobile applications using Burp Suite proxy to identify insecure API communications, authentication flaws, data leakage, and server-side vulnerabilities. Use when performing mobile application penetration testing, assessing API security, or evaluating client-server communication patterns. Activates for requests involving mobile traffic interception, Burp Suite mobile proxy, API security testing, or mobile HTTPS analysis.
|
| domain | cybersecurity |
| subdomain | mobile-security |
| author | mahipal |
| tags | ["mobile-security","android","ios","burp-suite","traffic-interception","penetration-testing"] |
| version | 1.0.0 |
| license | Apache-2.0 |
| nist_csf | ["PR.PS-01","PR.AA-05","ID.RA-01","DE.CM-09"] |
Intercepting Mobile Traffic with Burp Suite
When to Use
Use this skill when:
- Testing mobile application API endpoints for authentication, authorization, and injection vulnerabilities
- Analyzing data transmitted between mobile apps and backend servers during penetration tests
- Evaluating certificate pinning implementations and their bypass difficulty
- Identifying sensitive data leakage in mobile network traffic
Do not use this skill to intercept traffic from applications you are not authorized to test -- traffic interception without authorization violates computer fraud laws.
Most Often Missed & How to Confirm
- Android 7+ user-CA distrust — the proxy "works" for the browser but app traffic is empty. Confirm the CA is installed as a system cert (or via Magisk) and that the target app's traffic appears, not just Chrome's.
- Certificate pinning masking traffic — confirm pinning (not proxy misconfig) is the cause by running an Objection/Frida bypass and seeing requests reappear.
- Certificate Transparency enforcement — some apps reject the MITM cert via CT. Confirm by checking for CT failures in logs and bypassing CT separately.
- Non-HTTP protocols — WebSocket/gRPC/MQTT won't show in Burp. Confirm with Wireshark that traffic exists on other channels.
- VPN-tunneled apps bypass device proxy — confirm by checking that no traffic reaches Burp despite a correct proxy, then redirect with iptables on a rooted device.
- Invisible proxying for non-proxy-aware clients — confirm by enabling it when CONNECT requests are missing from HTTP history.
Prerequisites
- Burp Suite Professional or Community Edition installed on testing workstation
- Android device/emulator or iOS device on the same network as Burp Suite host
- Burp Suite CA certificate installed on the target device
- For Android 7+: Network security config modification or Magisk module for system CA trust
- For SSL pinning bypass: Frida + Objection or custom Frida scripts
- Wi-Fi network where proxy configuration is possible
Workflow
Step 1: Configure Burp Suite Proxy Listener
Burp Suite > Proxy > Options > Proxy Listeners:
- Bind to address: All interfaces (or specific IP)
- Bind to port: 8080
- Enable "Support invisible proxying"
Verify the listener is active and note the workstation's IP address on the shared network.
Step 2: Configure Mobile Device Proxy
