[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M798DG2VQXTAD47E3TB6RGAM":3,"skill-same:01M798DG2VQXTAD47E3TB6RGAM":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M798DG2VQXTAD47E3TB6RGAM","flutter",null,"Flutter app reversing and SSL pinning bypass — reFlutter Dart-AOT patching, BoringSSL bypass, libapp.so static analysis in Ghidra\u002Fradare2, Dart snapshot dump, and iOS Flutter.framework notes.","7ShIkI3\u002FDecepticon-x-DarkTriad","7ShIkI3","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78133376?v=4","01M797CTK5AHH2161YVG93NJ3B","Raphael Pascaud","01M797CTKRQS64R01J7E6TJSEM",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fmobile\u002Fflutter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: flutter\ndescription: Flutter app reversing and SSL pinning bypass — reFlutter Dart-AOT patching, BoringSSL bypass, libapp.so static analysis in Ghidra\u002Fradare2, Dart snapshot dump, and iOS Flutter.framework notes.\nallowed-tools: Bash Read Write\nmetadata:\n  subdomain: mobile\n  when_to_use: \"flutter dart aot libapp.so libflutter reflutter boringssl ssl pinning bypass snapshot dump cross-platform jadx-useless tunproxy uber-apk-signer\"\n  tags: flutter, dart, reflutter, ssl-pinning, reverse-engineering, libapp, boringssl\n  mitre_attack: T1635, T1521.003, T1406\n---\n\n# Flutter App Reversing Playbook\n\n> Flutter compiles Dart AOT to a native shared library (`libapp.so` \u002F\n> `Flutter.framework`). `jadx` \u002F `apktool` show only the thin Java\u002FObjC\n> shell and are useless for app logic. Use this playbook when static\n> Android or iOS skills yield nothing but an empty Java wrapper.\n\n## Prerequisites\n\n- APK \u002F IPA obtained (see `mobile\u002Fandroid\u002FSKILL.md` Path 1 for APK pull).\n- Tools: `reflutter` (`pip install reflutter`), `uber-apk-signer`\n  (download JAR from GitHub releases), `adb` + device or emulator,\n  `jadx` (identification only), Burp Suite proxy.\n- For iOS: `reFlutter` also patches `Flutter.framework`; use\n  `objection patchipa` or direct framework patching workflow.\n\n## Step 1: Identify a Flutter App\n\n```bash\n# Unzip APK, look for the telltale Flutter artifacts\nunzip -o base.apk -d \u002Ftmp\u002Fapk-out\u002F\n\nls \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002F\n# Flutter app: libflutter.so  libapp.so\n# Present:     flutter_assets\u002F   kernel_blob.bin (optional, debug)\n\n# jadx shows only the Java bootstrap:\njadx -d \u002Ftmp\u002Fapk-java \u002Ftmp\u002Fbase.apk\n# Expect: ~1 class, LoadLibrary(\"app\"), nothing useful\n\n# Confirm with strings:\nstrings \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibflutter.so | grep -i \"flutter\"\nstrings \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so | grep -E \"https?:\u002F\u002F\"\n```\n\nKey tell: `libapp.so` size > 5 MB with no dex business logic; the\n`kernel_blob.bin` in `flutter_assets\u002F` indicates a debug\u002FJIT build\n(rare in production; can extract Dart directly with `dart_vm`).\n\n## Step 2: reFlutter Workflow — Patch BoringSSL Pinning\n\nreFlutter patches the `ssl_crypto_x509_session_verify_cert_chain`\nfunction in `libflutter.so` to always return `true`, bypassing all\nBoringSSL-based certificate validation (covers both custom pinning\nand system trust).\n\n### Flutter \u003C= 3.23.x (hardcoded proxy IP)\n\n```bash\n# Patch: supply your Burp listener IP\nreflutter base.apk\n\n# reFlutter prompts for IP — enter your Burp machine IP (e.g. 192.168.1.100)\n# Output: release.RE.apk (patched, unsigned)\n\n# Sign with uber-apk-signer\njava -jar uber-apk-signer.jar --allowResign -a release.RE.apk -o \u002Ftmp\u002F\n\n# Install on device\nadb install \u002Ftmp\u002Frelease.RE-aligned-signed.apk\n\n# Configure Burp proxy listener on 0.0.0.0:8083 (reFlutter default port is 8083)\n# Launch app — HTTPS traffic appears in Burp\n```\n\n### Flutter >= 3.24.0 (no hardcoded proxy IP — breaking change)\n\nStarting Flutter 3.24.0 (August 2024), the hardcoded proxy IP was\nremoved from the patched BoringSSL stub. Traffic is no longer\nredirected to a fixed IP. Two options:\n\n**Option A: Device-level proxy**\n```bash\n# Patch as above (no IP prompt in 3.24+)\nreflutter base.apk\njava -jar uber-apk-signer.jar --allowResign -a release.RE.apk -o \u002Ftmp\u002F\n\n# Install and configure device proxy manually:\n# Android Settings → Wi-Fi → [SSID] → Proxy → Manual\n# Host: \u003CBurp-IP>  Port: 8080\n\n# Or use TunProxy for non-proxy-aware processes:\nadb install TunProxy.apk\n# Launch TunProxy, set server to \u003CBurp-IP>:8080, toggle VPN\n# Then launch patched app\n```\n\n**Option B: Per-app proxy injection via Frida**\n```bash\n# Run patched APK + Frida script to redirect all socket connections\nfrida -U -f com.target.app -l proxy-redirect.js --no-pause\n# proxy-redirect.js: hooks connect() syscall, redirects to Burp IP\n```\n\n### iOS Flutter.framework patching\n\n```bash\n# Extract IPA\nunzip target.ipa -d \u002Ftmp\u002Fipa-out\u002F\n# Locate Flutter.framework\nls \u002Ftmp\u002Fipa-out\u002FPayload\u002FTargetApp.app\u002FFrameworks\u002FFlutter.framework\u002FFlutter\n\n# reFlutter iOS (experimental — check reFlutter README for current support)\nreflutter target.ipa\n# Sign with codesign + adhoc or with valid mobileprovision\ncodesign --force --sign - \u002Ftmp\u002Fipa-out\u002FPayload\u002FTargetApp.app\u002FFrameworks\u002FFlutter.framework\u002FFlutter\n# Repack + install with ios-deploy or Sideloadly\n```\n\n## Step 3: BoringSSL Bypass Mechanism\n\nreFlutter patches `ssl_crypto_x509_session_verify_cert_chain` to\nunconditionally return `1` (success). This function is the central\nchain verification entry point in BoringSSL (the TLS library embedded\nin `libflutter.so`) — no root CA, no pinning config, and no custom\nvalidator override this patch because the chain evaluation never runs.\n\n**Manual binary patch (if reFlutter fails on a specific version):**\n```bash\n# Find the function offset in libflutter.so\nr2 -A \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibflutter.so\n# In r2: afl~ssl_crypto_x509\n# Or: \u002Fc ret  in data section near ssl_crypto_x509_session_verify_cert_chain\n\n# Patch: overwrite function prologue with MOV W0, #1 \u002F RET (AArch64)\n# MOV W0, 1 = 20 00 80 52\n# RET        = C0 03 5F D6\npython3 -c \"\nimport struct\nwith open('libflutter.so', 'r+b') as f:\n    f.seek(\u003Coffset>)\n    f.write(b'\\x20\\x00\\x80\\x52\\xC0\\x03\\x5F\\xD6')\n\"\n```\n\n## Step 4: Static Native RE — libapp.so in Ghidra \u002F radare2\n\n```bash\n# Load libapp.so in radare2 for quick triage\nr2 -A \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so\n\n# Strings — API endpoints, Firebase config, hardcoded keys\nr2 -qc 'iz~https' \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so\nr2 -qc 'iz~firebase' \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so\nr2 -qc 'iz~AIza' \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so   # Firebase API key prefix\n\n# Imports — identify Flutter plugins with native bridges\nr2 -qc 'ii' \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so | head -40\n```\n\nIn Ghidra (MCP-connected via `ghidra` server):\n```\n# connect_instance first, then batch analyze\n# Load libapp.so → auto-analyze\n# Search defined strings for URL patterns, credential patterns\n# Dart AOT functions are not named — use string xrefs to find handlers\n```\n\nDart AOT functions lack names (no symbol table in release builds) but\nthe Dart snapshot contains type metadata that `Il2CppDumper`-style\ntools and `dart_vm` snapshot parsers can partially recover (see\nsnapshot dump section below).\n\n## Step 5: Dart Snapshot Dump (Hit-or-Miss)\n\n```bash\n# Option 1: runtime adb pull from memory-mapped snapshot\nadb shell \"run-as com.target.app cat \u002Fdata\u002Fdata\u002Fcom.target.app\u002Fapp_flutter\u002Fsnapshot_blob.bin\" \\\n  > \u002Ftmp\u002Fsnapshot_blob.bin 2>\u002Fdev\u002Fnull\n\n# Option 2: use Dart VM snapshot reader tools\n# dart_snapshot_parser (community; partial support for Dart 2.x-3.x)\npip install dart-snapshot-parser 2>\u002Fdev\u002Fnull || true\n\n# Option 3: reFlutter's snapshot output\n# After running reFlutter and launching the patched app once,\n# reFlutter dumps snapshot_hash.txt which can seed symbol recovery tools\n```\n\n**Caveats**: Dart snapshot format changed in Dart 2.15, 3.0, and 3.4.\nCommunity parsers (snapshot_inspector, etc.) are often version-specific\nand may produce partial or no output on latest Flutter. Treat snapshot\ndump as a best-effort step; static string analysis is more reliable.\n\n## Step 6: Flutter Plugin Identification\n\nFlutter plugins use platform channels with predictable naming:\n\n```bash\n# Find channel names in libapp.so strings\nstrings \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so | grep -E \"plugins\\.|flutter\\.\" | sort -u\n\n# Channel names like:\n#   com.google.firebase.messaging       → push tokens\n#   plugins.flutter.io\u002Fpath_provider   → storage paths\n#   flutter.baseflow.com\u002Fgeolocator    → GPS\n#   plugins.flutter.io\u002Flocal_auth      → biometric\n\n# Cross-reference with flutter_assets\u002FAssetManifest.json\ncat \u002Ftmp\u002Fapk-out\u002Fflutter_assets\u002FAssetManifest.json | python3 -m json.tool | head\n```\n\n## Evidence\n\n```python\nkg_add_node(\n    kind=\"finding\",\n    label=\"Flutter BoringSSL pinning bypassed\",\n    props={\n        \"key\": f\"flutter-boringssl-bypass::{package_id}\",\n        \"severity\": \"high\",\n        \"cvss\": 7.4,\n        \"package\": package_id,\n        \"flutter_version\": \"\u003Cversion-from-libflutter-strings>\",\n        \"bypass_method\": \"reFlutter\",\n        \"proxy_verified\": True,\n    },\n)\n```\n\n## ZFP\n\n1. Burp HTTP history showing decrypted HTTPS from patched Flutter app.\n2. `strings libapp.so | grep https` output showing extracted endpoints.\n3. Screenshot of reFlutter build output + uber-apk-signer signing\n   confirming the patched APK was installed.\n\n## OPSEC Notes\n\n- reFlutter requires re-signing the APK; app integrity checks (Google\n  Play Integrity API, SafetyNet) will flag the modified signature.\n  Use emulator or device without Play Store for testing.\n- The patched APK has a different certificate than the original; side-\n  load via `adb install` or `adb install --bypass-low-target-sdk-block`.\n- For production devices, TunProxy routes traffic at the VPN layer\n  without modifying the APK signature.\n- libflutter.so binary patching is version-specific; wrong offset\n  crashes the app. Always test on a throwaway device\u002Femulator first.\n\n## Severity Table\n\n| Bug | Severity |\n|---|---|\n| No certificate validation (BoringSSL patched trivially) | High 7.4 |\n| Hardcoded API key \u002F Firebase config in libapp.so strings | Critical 9.0 |\n| Sensitive data in Dart snapshot \u002F kernel_blob | High 7.5 |\n| Flutter plugin channel unauthenticated method call | Medium-High |\n\n## References\n\n- reFlutter: https:\u002F\u002Fgithub.com\u002Fptswarm\u002FreFlutter\n- Flutter 3.24.0 proxy change: https:\u002F\u002Fgithub.com\u002Fptswarm\u002FreFlutter\u002Fissues\u002F107\n- TunProxy (Android): https:\u002F\u002Fgithub.com\u002Fraise-isayan\u002FTunProxy\n- uber-apk-signer: https:\u002F\u002Fgithub.com\u002Fpatrickfav\u002Fuber-apk-signer\n- kayssel \"Breaking Flutter\" guide: https:\u002F\u002Fblog.nviso.eu\u002F2022\u002F08\u002F18\u002Fintercept-flutter-traffic-on-ios-and-android-http-https-edition\u002F\n- Cross-ref: `mobile\u002Fandroid\u002FSKILL.md` (APK pull), `mobile\u002Fios\u002Fdynamic\u002FSKILL.md` (iOS BoringSSL path)\n","# Flutter App Reversing Playbook\n\n> Flutter compiles Dart AOT to a native shared library (`libapp.so` \u002F\n> `Flutter.framework`). `jadx` \u002F `apktool` show only the thin Java\u002FObjC\n> shell and are useless for app logic. Use this playbook when static\n> Android or iOS skills yield nothing but an empty Java wrapper.\n\n## Prerequisites\n\n- APK \u002F IPA obtained (see `mobile\u002Fandroid\u002FSKILL.md` Path 1 for APK pull).\n- Tools: `reflutter` (`pip install reflutter`), `uber-apk-signer`\n  (download JAR from GitHub releases), `adb` + device or emulator,\n  `jadx` (identification only), Burp Suite proxy.\n- For iOS: `reFlutter` also patches `Flutter.framework`; use\n  `objection patchipa` or direct framework patching workflow.\n\n## Step 1: Identify a Flutter App\n\n```bash\n# Unzip APK, look for the telltale Flutter artifacts\nunzip -o base.apk -d \u002Ftmp\u002Fapk-out\u002F\n\nls \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002F\n# Flutter app: libflutter.so  libapp.so\n# Present:     flutter_assets\u002F   kernel_blob.bin (optional, debug)\n\n# jadx shows only the Java bootstrap:\njadx -d \u002Ftmp\u002Fapk-java \u002Ftmp\u002Fbase.apk\n# Expect: ~1 class, LoadLibrary(\"app\"), nothing useful\n\n# Confirm with strings:\nstrings \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibflutter.so | grep -i \"flutter\"\nstrings \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so | grep -E \"https?:\u002F\u002F\"\n```\n\nKey tell: `libapp.so` size > 5 MB with no dex business logic; the\n`kernel_blob.bin` in `flutter_assets\u002F` indicates a debug\u002FJIT build\n(rare in production; can extract Dart directly with `dart_vm`).\n\n## Step 2: reFlutter Workflow — Patch BoringSSL Pinning\n\nreFlutter patches the `ssl_crypto_x509_session_verify_cert_chain`\nfunction in `libflutter.so` to always return `true`, bypassing all\nBoringSSL-based certificate validation (covers both custom pinning\nand system trust).\n\n### Flutter \u003C= 3.23.x (hardcoded proxy IP)\n\n```bash\n# Patch: supply your Burp listener IP\nreflutter base.apk\n\n# reFlutter prompts for IP — enter your Burp machine IP (e.g. 192.168.1.100)\n# Output: release.RE.apk (patched, unsigned)\n\n# Sign with uber-apk-signer\njava -jar uber-apk-signer.jar --allowResign -a release.RE.apk -o \u002Ftmp\u002F\n\n# Install on device\nadb install \u002Ftmp\u002Frelease.RE-aligned-signed.apk\n\n# Configure Burp proxy listener on 0.0.0.0:8083 (reFlutter default port is 8083)\n# Launch app — HTTPS traffic appears in Burp\n```\n\n### Flutter >= 3.24.0 (no hardcoded proxy IP — breaking change)\n\nStarting Flutter 3.24.0 (August 2024), the hardcoded proxy IP was\nremoved from the patched BoringSSL stub. Traffic is no longer\nredirected to a fixed IP. Two options:\n\n**Option A: Device-level proxy**\n```bash\n# Patch as above (no IP prompt in 3.24+)\nreflutter base.apk\njava -jar uber-apk-signer.jar --allowResign -a release.RE.apk -o \u002Ftmp\u002F\n\n# Install and configure device proxy manually:\n# Android Settings → Wi-Fi → [SSID] → Proxy → Manual\n# Host: \u003CBurp-IP>  Port: 8080\n\n# Or use TunProxy for non-proxy-aware processes:\nadb install TunProxy.apk\n# Launch TunProxy, set server to \u003CBurp-IP>:8080, toggle VPN\n# Then launch patched app\n```\n\n**Option B: Per-app proxy injection via Frida**\n```bash\n# Run patched APK + Frida script to redirect all socket connections\nfrida -U -f com.target.app -l proxy-redirect.js --no-pause\n# proxy-redirect.js: hooks connect() syscall, redirects to Burp IP\n```\n\n### iOS Flutter.framework patching\n\n```bash\n# Extract IPA\nunzip target.ipa -d \u002Ftmp\u002Fipa-out\u002F\n# Locate Flutter.framework\nls \u002Ftmp\u002Fipa-out\u002FPayload\u002FTargetApp.app\u002FFrameworks\u002FFlutter.framework\u002FFlutter\n\n# reFlutter iOS (experimental — check reFlutter README for current support)\nreflutter target.ipa\n# Sign with codesign + adhoc or with valid mobileprovision\ncodesign --force --sign - \u002Ftmp\u002Fipa-out\u002FPayload\u002FTargetApp.app\u002FFrameworks\u002FFlutter.framework\u002FFlutter\n# Repack + install with ios-deploy or Sideloadly\n```\n\n## Step 3: BoringSSL Bypass Mechanism\n\nreFlutter patches `ssl_crypto_x509_session_verify_cert_chain` to\nunconditionally return `1` (success). This function is the central\nchain verification entry point in BoringSSL (the TLS library embedded\nin `libflutter.so`) — no root CA, no pinning config, and no custom\nvalidator override this patch because the chain evaluation never runs.\n\n**Manual binary patch (if reFlutter fails on a specific version):**\n```bash\n# Find the function offset in libflutter.so\nr2 -A \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibflutter.so\n# In r2: afl~ssl_crypto_x509\n# Or: \u002Fc ret  in data section near ssl_crypto_x509_session_verify_cert_chain\n\n# Patch: overwrite function prologue with MOV W0, #1 \u002F RET (AArch64)\n# MOV W0, 1 = 20 00 80 52\n# RET        = C0 03 5F D6\npython3 -c \"\nimport struct\nwith open('libflutter.so', 'r+b') as f:\n    f.seek(\u003Coffset>)\n    f.write(b'\\x20\\x00\\x80\\x52\\xC0\\x03\\x5F\\xD6')\n\"\n```\n\n## Step 4: Static Native RE — libapp.so in Ghidra \u002F radare2\n\n```bash\n# Load libapp.so in radare2 for quick triage\nr2 -A \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so\n\n# Strings — API endpoints, Firebase config, hardcoded keys\nr2 -qc 'iz~https' \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so\nr2 -qc 'iz~firebase' \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so\nr2 -qc 'iz~AIza' \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so   # Firebase API key prefix\n\n# Imports — identify Flutter plugins with native bridges\nr2 -qc 'ii' \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so | head -40\n```\n\nIn Ghidra (MCP-connected via `ghidra` server):\n```\n# connect_instance first, then batch analyze\n# Load libapp.so → auto-analyze\n# Search defined strings for URL patterns, credential patterns\n# Dart AOT functions are not named — use string xrefs to find handlers\n```\n\nDart AOT functions lack names (no symbol table in release builds) but\nthe Dart snapshot contains type metadata that `Il2CppDumper`-style\ntools and `dart_vm` snapshot parsers can partially recover (see\nsnapshot dump section below).\n\n## Step 5: Dart Snapshot Dump (Hit-or-Miss)\n\n```bash\n# Option 1: runtime adb pull from memory-mapped snapshot\nadb shell \"run-as com.target.app cat \u002Fdata\u002Fdata\u002Fcom.target.app\u002Fapp_flutter\u002Fsnapshot_blob.bin\" \\\n  > \u002Ftmp\u002Fsnapshot_blob.bin 2>\u002Fdev\u002Fnull\n\n# Option 2: use Dart VM snapshot reader tools\n# dart_snapshot_parser (community; partial support for Dart 2.x-3.x)\npip install dart-snapshot-parser 2>\u002Fdev\u002Fnull || true\n\n# Option 3: reFlutter's snapshot output\n# After running reFlutter and launching the patched app once,\n# reFlutter dumps snapshot_hash.txt which can seed symbol recovery tools\n```\n\n**Caveats**: Dart snapshot format changed in Dart 2.15, 3.0, and 3.4.\nCommunity parsers (snapshot_inspector, etc.) are often version-specific\nand may produce partial or no output on latest Flutter. Treat snapshot\ndump as a best-effort step; static string analysis is more reliable.\n\n## Step 6: Flutter Plugin Identification\n\nFlutter plugins use platform channels with predictable naming:\n\n```bash\n# Find channel names in libapp.so strings\nstrings \u002Ftmp\u002Fapk-out\u002Flib\u002Farm64-v8a\u002Flibapp.so | grep -E \"plugins\\.|flutter\\.\" | sort -u\n\n# Channel names like:\n#   com.google.firebase.messaging       → push tokens\n#   plugins.flutter.io\u002Fpath_provider   → storage paths\n#   flutter.baseflow.com\u002Fgeolocator    → GPS\n#   plugins.flutter.io\u002Flocal_auth      → biometric\n\n# Cross-reference with flutter_assets\u002FAssetManifest.json\ncat \u002Ftmp\u002Fapk-out\u002Fflutter_assets\u002FAssetManifest.json | python3 -m json.tool | head\n```\n\n## Evidence\n\n```python\nkg_add_node(\n    kind=\"finding\",\n    label=\"Flutter BoringSSL pinning bypassed\",\n    props={\n        \"key\": f\"flutter-boringssl-bypass::{package_id}\",\n        \"severity\": \"high\",\n        \"cvss\": 7.4,\n        \"package\": package_id,\n        \"flutter_version\": \"\u003Cversion-from-libflutter-strings>\",\n        \"bypass_method\": \"reFlutter\",\n        \"proxy_verified\": True,\n    },\n)\n```\n\n## ZFP\n\n1. Burp HTTP history showing decrypted HTTPS from patched Flutter app.\n2. `strings libapp.so | grep https` output showing extracted endpoints.\n3. Screenshot of reFlutter build output + uber-apk-signer signing\n   confirming the patched APK was installed.\n\n## OPSEC Notes\n\n- reFlutter requires re-signing the APK; app integrity checks (Google\n  Play Integrity API, SafetyNet) will flag the modified signature.\n  Use emulator or device without Play Store for testing.\n- The patched APK has a different certificate than the original; side-\n  load via `adb install` or `adb install --bypass-low-target-sdk-block`.\n- For production devices, TunProxy routes traffic at the VPN layer\n  without modifying the APK signature.\n- libflutter.so binary patching is version-specific; wrong offset\n  crashes the app. Always test on a throwaway device\u002Femulator first.\n\n## Severity Table\n\n| Bug | Severity |\n|---|---|\n| No certificate validation (BoringSSL patched trivially) | High 7.4 |\n| Hardcoded API key \u002F Firebase config in libapp.so strings | Critical 9.0 |\n| Sensitive data in Dart snapshot \u002F kernel_blob | High 7.5 |\n| Flutter plugin channel unauthenticated method call | Medium-High |\n\n## References\n\n- reFlutter: https:\u002F\u002Fgithub.com\u002Fptswarm\u002FreFlutter\n- Flutter 3.24.0 proxy change: https:\u002F\u002Fgithub.com\u002Fptswarm\u002FreFlutter\u002Fissues\u002F107\n- TunProxy (Android): https:\u002F\u002Fgithub.com\u002Fraise-isayan\u002FTunProxy\n- uber-apk-signer: https:\u002F\u002Fgithub.com\u002Fpatrickfav\u002Fuber-apk-signer\n- kayssel \"Breaking Flutter\" guide: https:\u002F\u002Fblog.nviso.eu\u002F2022\u002F08\u002F18\u002Fintercept-flutter-traffic-on-ios-and-android-http-https-edition\u002F\n- Cross-ref: `mobile\u002Fandroid\u002FSKILL.md` (APK pull), `mobile\u002Fios\u002Fdynamic\u002FSKILL.md` (iOS BoringSSL path)\n",{"name":5,"metadata":24,"description":7,"allowed-tools":29},{"tags":25,"subdomain":26,"when_to_use":27,"mitre_attack":28},"flutter, dart, reflutter, ssl-pinning, reverse-engineering, libapp, boringssl","mobile","flutter dart aot libapp.so libflutter reflutter boringssl ssl pinning bypass snapshot dump cross-platform jadx-useless tunproxy uber-apk-signer","T1635, T1521.003, T1406","Bash Read Write","main","42b918525fb79065e730da3da997bffb33fcd414","packages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fmobile\u002Fflutter",0,"https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad","https:\u002F\u002Fgithub.com\u002F7ShIkI3","2026-07-22 19:02:27",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add 7ShIkI3\u002FDecepticon-x-DarkTriad --skill flutter",{"tool":43,"command":44},"bunx","bunx skills add 7ShIkI3\u002FDecepticon-x-DarkTriad --skill flutter",{"tool":46,"command":47},"pnpm","pnpm dlx skills add 7ShIkI3\u002FDecepticon-x-DarkTriad --skill flutter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fmobile\u002Fflutter\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M798TNHEBA4Y67TJJ7W0KBDD","wps-pixie-dust","WPS Pixie-Dust offline nonce attack (reaver -K \u002F pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.","https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M798TH79VR8XM7AAMG0ZKSXX","wpa3-sae","WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.","https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M798TD0E10ZHQN5X362M4HG9","wpa2-psk","WPA\u002FWPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer\u002FSMB encryption mode in 2026.","https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M798T7HFR3NB9WJTK1FESVF9","wpa-enterprise-eap","WPA\u002FWPA2\u002FWPA3-Enterprise (802.1X\u002FEAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.","https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M798T38B4SV0T87VQK56KPHC","krack-fragattacks","KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation\u002Faggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.","https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M798SXTNF0RP1DXKQEWFVQ9H","evil-twin-karma","Evil-twin rogue AP with KARMA\u002FMana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK\u002Fopen networks. Distinct from wpa-enterprise-eap which targets 802.1X.","https:\u002F\u002Fgithub.com\u002F7ShIkI3\u002FDecepticon-x-DarkTriad\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]