Перейти к содержимому
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
mukul975/intercepting-mobile-traffic-with-burpsuiteМобильные устройства, прошивки и железо

intercepting-mobile-traffic-with-burpsuite

⁨Intercepts and analyzes HTTP/HTTPS traffic from mobile applications⁩

v1.0.03 установки+3 за 7 дней36,3 тыс. ЗвездыApache-2.0синхронизировано 12 часов назад

Установка

Ещё нет NotHoly CLI? Сначала установите её.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/intercepting-mobile-traffic-with-burpsuite

Пишет в ⁦~/.notholy/skills⁩ после проверки подписи и SHA-256.

ПодписьПодписано, ed25519
RD9E7c4vUW…EZpGaiAg==CLI проверяет SHA-256 и подпись, прежде чем записать хоть один файл.
Пакет8b74e38e…513fd93d
8b74e38ec469…7374513fd93d8 файлов · ⁦13.6 KB⁩
ПроверкаСредний3 замечания
  • Исполняемый скрипт в составе навыкаscripts/agent.py
  • Исполняемый скрипт в составе навыкаscripts/process.py
  • Ссылки на внешние домены
Вся проверка
Источникgithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/intercepting-mobile-traffic-with-burpsuite@54a7988

Эта запись еще не переведена на русский, поэтому показан текст на другом языке: English.

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.

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

text
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

Android:

text
Settings > Wi-Fi > [Network] > Advanced > Manual Proxy
- Host: <burp_workstation_ip>
- Port: 8080

iOS:

text
Settings > Wi-Fi > [Network] > Configure Proxy > Manual
- Server: <burp_workstation_ip>
- Port: 8080

Step 3: Install Burp Suite CA Certificate

Android (below API 24):

bash
# Export Burp CA from Proxy > Options > Import/Export CA Certificate
# Transfer to device and install via Settings > Security > Install from storage

Android (API 24+ / Android 7+): Apps targeting API 24+ do not trust user-installed CAs by default. Options:

bash
# Option A: Modify app's network_security_config.xml (requires APK rebuild)
# Add to res/xml/network_security_config.xml:
# <network-security-config>
#   <debug-overrides>
#     <trust-anchors>
#       <certificates src="user" />
#     </trust-anchors>
#   </debug-overrides>
# </network-security-config>

# Option B: Install as system CA (rooted device)
openssl x509 -inform DER -in burp-ca.der -out burp-ca.pem
HASH=$(openssl x509 -inform PEM -subject_hash_old -in burp-ca.pem | head -1)
cp burp-ca.pem "$HASH.0"
adb push "$HASH.0" /system/etc/security/cacerts/
adb shell chmod 644 /system/etc/security/cacerts/$HASH.0

# Option C: Magisk module (MagiskTrustUserCerts)

iOS:

text
1. Navigate to http://<burp_ip>:8080 in Safari
2. Download Burp CA certificate
3. Settings > General > VPN & Device Management > Install profile
4. Settings > General > About > Certificate Trust Settings > Enable full trust

Step 4: Intercept and Analyze Traffic

With proxy configured, open the target app and navigate through its functionality:

Burp Suite > Proxy > HTTP History: Review all captured requests and responses.

Key areas to analyze:

  • Authentication tokens: JWT structure, token expiration, refresh mechanisms
  • API endpoints: RESTful paths, GraphQL queries, parameter patterns
  • Sensitive data in transit: PII, credentials, financial data
  • Response headers: Security headers (HSTS, CSP, X-Frame-Options)
  • Error responses: Stack traces, debug information, internal paths

Step 5: Test API Vulnerabilities Using Burp Repeater

Forward intercepted requests to Repeater for manual testing:

text
Right-click request > Send to Repeater

Test categories:
- Authentication bypass: Remove/modify auth tokens
- IDOR: Modify user IDs, object references
- Injection: SQL injection, NoSQL injection in parameters
- Rate limiting: Rapid request replay for brute force assessment
- Business logic: Modify prices, quantities, permissions in requests

Step 6: Automate Testing with Burp Scanner

text
Right-click request > Do active scan (Professional only)

Scanner checks:
- SQL injection (error-based, blind, time-based)
- XSS (reflected, stored)
- Command injection
- Path traversal
- XML/JSON injection
- Authentication flaws

Step 7: Handle Certificate Pinning

If traffic is not visible due to certificate pinning:

bash
# Frida-based bypass (generic)
frida -U -f com.target.app -l ssl-pinning-bypass.js

# Objection bypass
objection --gadget com.target.app explore
ios sslpinning disable  # or
android sslpinning disable

Key Concepts

Term Definition
MITM Proxy Man-in-the-middle proxy that terminates and re-establishes TLS connections to inspect encrypted traffic
Certificate Pinning Client-side validation that restricts accepted server certificates beyond the OS trust store
Network Security Config Android XML configuration controlling app trust anchors, cleartext traffic policy, and certificate pinning
Invisible Proxying Burp feature handling non-proxy-aware clients that don't send CONNECT requests
IDOR Insecure Direct Object Reference -- accessing resources by manipulating identifiers without authorization checks

Tools & Systems

  • Burp Suite Professional: Full-featured web application security testing proxy with active scanner
  • Burp Suite Community: Free version with manual interception and basic tools
  • Frida: Dynamic instrumentation for runtime SSL pinning bypass
  • mitmproxy: Open-source alternative to Burp Suite for programmatic traffic analysis
  • Charles Proxy: Alternative HTTP proxy with mobile-friendly certificate installation

Common Pitfalls

  • Android 7+ CA trust: User-installed certificates are not trusted by apps targeting API 24+. Must use system CA installation or app modification.
  • Certificate transparency: Some apps use Certificate Transparency logs to detect MITM. Check for CT enforcement in the app.
  • Non-HTTP protocols: Burp Suite only handles HTTP/HTTPS. Use Wireshark for WebSocket, MQTT, gRPC, or custom binary protocols.
  • VPN-based apps: Apps using VPN tunnels bypass device proxy settings. May need iptables rules on a rooted device to redirect traffic.

Файлы этой версии

Права

ПравоЗаявленоНайдено проверкой
Читает файлыНетНет
Пишет файлыДаДа
Выполняет команды shellДаДа
Ходит в сетьДаДа
Использует коннекторыНетНет
Управляет браузеромНетНет

Замечания проверки

Проверено 13 нояб. 2026 г.

  1. СредняяФайл · Исполняемый скрипт в составе навыкаscripts/agent.py
  2. СредняяФайл · Исполняемый скрипт в составе навыкаscripts/process.py
  3. ИнфоСсылка · Ссылки на внешние домены

Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.

ВерсияОпубликованаКоммитSHA-256ПодписьИзменение прав
v1.0.013 нояб. 2026 г.54a79888b74e38eПодписана–

Спрашивайте обо всём, что позволяет ваш скоуп.

Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.

  1. 1/3

    Создайте аккаунт

    Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.

    ЛичныйКомпания
  2. 2/3

    Пополните баланс

    Картой. Оплата за токены, без подписки.

    $5.00минимальное пополнение
  3. 3/3

    Спрашивайте

    В чате, или установите CLI и выполните notholy login в терминале.

    $ notholy login