android-crossplatform-flutter-rn-xamarin
Test cross-platform Android apps — Flutter (reFlutter/native BoringSSL hooks, Dart ignores system proxy & user CA), React Native (extract and beautify the JS bundle for secrets/logic), and Xamarin (decompile .NET assemblies). Tier 1. Use when the app is built on a cross-platform framework. Aligns to OWASP MASTG.
AnandJogawade · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add AnandJogawade/Zazy-Pentest-Plugin-for-Claude --skill android-crossplatform-flutter-rn-xamarin技能说明
name: android-crossplatform-flutter-rn-xamarin description: Test cross-platform Android apps — Flutter (reFlutter/native BoringSSL hooks, Dart ignores system proxy & user CA), React Native (extract and beautify the JS bundle for secrets/logic), and Xamarin (decompile .NET assemblies). Tier 1. Use when the app is built on a cross-platform framework. Aligns to OWASP MASTG.
Cross-Platform Apps — Flutter / React Native / Xamarin
Framework "opacity" is not security. Detect the framework, then use the framework-specific path to intercept traffic and recover secrets/logic.
Trigger phrases
flutter, reflutter, react native, index.android.bundle, xamarin, mono assemblies, dart ssl, libapp.so, cross platform app, blutter
Method
- Identify the framework (unzip the APK):
- Flutter →
lib/<abi>/libapp.so+libflutter.so,assets/flutter_assets/kernel_blob.bin. - React Native →
assets/index.android.bundle. - Xamarin →
assemblies/*.dll(Mono).
- Flutter →
- Flutter (Dart ignores system proxy & user CA; TLS in BoringSSL):
strings lib/arm64-v8a/libapp.so | grep -iE "api|key|http"reflutter app.apk— repackages to route traffic / disable pinning, then re-sign + install.- Native pinning hook:
frida -U -f <package> -l flutter-ssl-bypass.js --no-pause(hooks the engine'sSSL_CTX_set_custom_verify). - Deeper static reversing: Blutter on
libapp.so.
- React Native:
unzip -o app.apk assets/index.android.bundle -d rn && npx prettier rn/index.android.bundle | less- Grep the bundle for endpoints/keys/logic; check for dev mode / exposed debugging.
- Xamarin: decompile
assemblies/*.dllwith dnSpy/ILSpy for logic, secrets, and pinning code.
Modern / rare techniques
- [NEW/RARE] Flutter proxy/CA bypass — standard Java
TrustManager+ device proxy do NOT apply; must use reFlutter or a native BoringSSL Frida hook. - [NEW/RARE] RN JS bundle mining — bundles routinely embed endpoints, API keys, and full client logic; dev-mode bundles may expose a debugger.
- [NEW/RARE] Xamarin .NET assemblies decompile cleanly to near-source — treat like any .NET review.
Bypass / evasion
If reFlutter's repackaged APK is rejected by anti-tamper, fall back to the runtime BoringSSL Frida hook (+ android-root-antidebug-bypass first). For RN, if the bundle is Hermes-compiled, disassemble the .hbc with hermes-dec instead of beautifying JS.
Escalation / chaining
Framework-specific pinning bypass unlocks android-network-cleartext-tls + android-backend-api-testing; recovered secrets → android-secrets-hardcoded / cloud-pentest. Native Flutter work chains with android-native-lib-analysis and android-frida-objection-instrumentation.
Backend & tooling
Preferred Kali path (native Kali / WSL+Kali / Kali-SSH / Kali-MCP / HexStrike). Needs the user's device/emulator (frida-server; reFlutter re-install) + Kali tooling (reFlutter/Blutter/Frida/dnSpy/ILSpy/prettier) + Burp/mitmproxy. Windows-local last resort. See zazy-orchestrator.
Verification (background, before reporting)
Confirm traffic is actually captured after the framework-specific bypass (a real request/response in the proxy), and that recovered secrets are live, before marking CONFIRMED. Reproduce independently.
Evidence
The framework fingerprint, the bypass used (reFlutter/Frida/decompile), captured traffic, and secrets/logic recovered from the bundle/assembly/libapp.so. Remediation: server-side secrets; framework-aware pinning; strip RN dev/debug; obfuscate .NET; don't rely on framework opacity.