intercept
Intelligent traffic interception — SSL bypass, HTTP logging, traffic collection
v2026.7.31-4eb5d2f3 instalaciones+3 en 7 días76 EstrellasMITsincronizado hace 12 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install theqmaks/interceptEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquetef84b3a7d…05b7f342
f84b3a7de19a…b7dd05b7f3421 archivo · 2.3 KBEscaneoBajo1 hallazgo
- Enlaces a dominios externos
Fuentegithub.com/TheQmaks/areclaw/tree/main/.claude/skills/intercept@4eb5d2f
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
You are setting up intelligent traffic interception. Not just "run mitmproxy" — choose the right strategy based on the app's protections.
Input
$ARGUMENTS— package name (must be installed on device)
Phase 1: Reconnaissance
1a. Check network security config
# Decompile resources
java -jar tools/apktool/apktool.jar d -s -f -o /tmp/intercept_recon $APKRead res/xml/network_security_config.xml:
<domain-config cleartextTrafficPermitted="false">→ HTTPS only<pin-set>→ Certificate pinning configured<trust-anchors><certificates src="user"/>→ User CA trusted (easy mode!)- No config file → default (user CA NOT trusted on Android 7+)
1b. Detect pinning implementation
grep -rn 'CertificatePinner\|TrustManager\|X509\|ssl_pinning\|NetworkSecurityConfig' workspace/output/$PKG/Determine pinning type:
- None → Simple proxy is enough
- OkHttp CertificatePinner → ssl-bypass.js handles it
- Custom X509TrustManager → ssl-bypass.js handles it
- Conscrypt/platform → ssl-bypass.js handles it
- Native TLS (BoringSSL in .so) → Need Interceptor hook on
SSL_CTX_set_verify - Flutter → Need special Flutter SSL bypass
- React Native → Patch network_security_config + ssl-bypass.js
Phase 2: Strategy Selection
Based on recon, choose approach:
Strategy A: No Pinning
# Just log with Frida (simplest, no proxy needed)
frida -U -f $PKG -l workspace/frida-scripts/http-logger.jsStrategy B: Standard Pinning (OkHttp/TrustManager/Conscrypt)
# SSL bypass + HTTP logging
frida -U -f $PKG \
-l workspace/frida-scripts/ssl-bypass.js \
-l workspace/frida-scripts/http-logger.jsStrategy C: Heavy Pinning + Root Detection
# Full bypass stack
frida -U -f $PKG \
-l workspace/frida-scripts/root-bypass.js \
-l workspace/frida-scripts/ssl-bypass.js \
-l workspace/frida-scripts/http-logger.jsStrategy C2: App Detects Frida (crash/illegal instruction on attach)
Use phantom-frida stealth server. Read tools/phantom-frida/build-info.json for name and port:
# Parse config
cat tools/phantom-frida/build-info.json
# → {"name": "<NAME>", "port": <PORT>, ...}
# Deploy phantom-frida to device (if not already running)
adb push tools/phantom-frida/<NAME>-server /data/local/tmp/<NAME>-server
adb shell chmod 755 /data/local/tmp/<NAME>-server
adb shell /data/local/tmp/<NAME>-server -D &
adb forward tcp:<PORT> tcp:<PORT>
# Use -H instead of -U (custom port)
frida -H 127.0.0.1:<PORT> -f $PKG \
-l workspace/frida-scripts/ssl-bypass.js \
-l workspace/frida-scripts/http-logger.jsSigns that app detects Frida: crashes immediately on frida -U, "illegal instruction" error,
app shows "security check failed", or app force-closes when Frida attaches.
Strategy D: Native/Custom Pinning
Write a custom Frida script to hook the specific pinning implementation found in recon. May need to hook native functions in specific .so files.
Strategy E: mitmproxy (for full request/response bodies)
# Start mitmproxy with HAR dump
mitmdump -w workspace/traffic/$PKG.har --set stream_large_bodies=10m
# Configure device proxy
adb shell settings put global http_proxy <computer_ip>:8080
# Then bypass pinning
frida -U -f $PKG -l workspace/frida-scripts/ssl-bypass.jsPhase 3: Traffic Collection
3a. Start interception
Launch chosen strategy from Phase 2.
3b. Navigate the app
# Automated navigation
python pytools/ui_explorer.py snapshot # See current state
# Walk key flows:
# - App startup (splash → main screen)
# - Login/registration
# - Main features
# - Settings
# - ProfileSpend adequate time on each screen. Some API calls happen on timers or scroll events.
3c. Save traffic
If using http-logger.js, output goes to console. Capture it:
frida -U -f $PKG -l workspace/frida-scripts/ssl-bypass.js -l workspace/frida-scripts/http-logger.js 2>&1 | tee workspace/traffic/$PKG-raw.log
# Extract HTTP-LOG lines
grep '^\[HTTP-LOG\]' workspace/traffic/$PKG-raw.log | sed 's/^\[HTTP-LOG\] //' > workspace/traffic/$PKG-traffic.jsonPhase 4: Results
4a. Generate Postman collection
python pytools/traffic_to_collection.py frida workspace/traffic/$PKG-traffic.json \
--name "$PKG API" \
--output workspace/collections/$PKG.json4b. Generate OpenAPI spec (if mitmproxy was used)
# If traffic was captured via mitmproxy (not Frida http-logger)
mitmproxy2swagger -i workspace/traffic/$PKG.flow -o workspace/collections/$PKG-api.yaml \
-p https://api.example.com --examples4c. Summary
Report to user:
- Number of unique endpoints discovered
- Base URLs found
- Auth mechanism detected
- Notable findings (interesting headers, tokens, unexpected calls)
- Path to traffic file and Postman collection
Phase 5: Cleanup
# Remove proxy if set
adb shell settings put global http_proxy :0Archivos de esta versión
- SKILL.md5.1 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | Sí | Sí |
| Escribe archivos | Sí | Sí |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.7.31-4eb5d2f | 13 nov 2026 | 4eb5d2f | f84b3a7d | Firmada | – |
Más de TheQmaks
Todo de este publicadorMás en Red, wireless y telecom
Ver la categoría- performing-network-packet-capture-analysismukul975/performing-network-packet-capture-analysis4
- network-segmentation-reviewsecurityskills/network-segmentation-review3
- performing-ssl-stripping-attackmukul975/performing-ssl-stripping-attack3
- implementing-next-generation-firewall-with-palo-altomukul975/implementing-next-generation-firewall-with-palo-alto3
- configuring-zscaler-private-access-for-ztnamukul975/configuring-zscaler-private-access-for-ztna3
- implementing-canary-tokens-for-network-intrusionmukul975/implementing-canary-tokens-for-network-intrusion3
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login