reverse-flutter-analysis

name	reverse-flutter-analysis
description	End-to-end authorized Flutter APK reverse-engineering workflow. Use when Codex needs to analyze a Flutter Android APK with apktool, MobSF/mobsfscan, jadx, Blutter, reFlutter, Burp Suite, Frida, objection, Android signing tools, or when creating reports from case artifacts in this reverse-flutter repository.

Reverse Flutter Analysis

Operating Rules

Work only on APKs the user owns or is explicitly authorized to test. Keep evidence grounded in files under cases/<case>/. Do not invent package names, endpoints, tokens, or findings.

Case data may contain secrets and proprietary code. Do not commit cases/, APKs, keystores, Burp captures, or reports unless the user explicitly requests it after review.

Workflow

1. Verify tooling:

make check

2. Create a case:

make new CASE=<case> APK=/absolute/path/app.apk

3. Run static analysis:

make static CASE=<case>
make blutter CASE=<case>

4. Run MobSF:

• Use make mobsf-upload CASE=<case> only when .env has MOBSF_API_KEY.
• Otherwise follow docs/MOBSF.md and save exports under cases/<case>/static/mobsf/.

5. Prepare dynamic analysis:

make reflutter CASE=<case> BURP_HOST=<computer-lan-ip>
make sign CASE=<case>

Install the signed APK from cases/<case>/patched/.

6. Configure GUI-only tools:

• Read docs/BURP.md for Burp listener menu steps.
• Use port 8083.
• Bind to All interfaces.
• Enable invisible proxying.

7. Run runtime hooks:

make frida-server
make hook-ssl CASE=<case>
make hook-root CASE=<case>
make objection-explore CASE=<case>

If package detection failed, pass PACKAGE=<id> to Make.

8. Draft the report:

make report CASE=<case>

Use prompts/report-template.md and evidence under the case directory.

Evidence Priority

Prefer artifacts in this order:

1. Runtime proof from Burp, Frida, objection logs.
2. Blutter object/function output and generated blutter_frida.js.
3. MobSF export and mobsfscan.json.
4. apktool manifest/assets and JADX source.
5. Inferences, clearly labeled as such.

References

Read these only when needed:

• references/evidence-map.md for expected files and where to look.
• references/manual-gui.md for GUI-only Burp and MobSF steps.