competition-android-hooking

1# Competition Android Hooking
2 
3Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.
4 
5Use this skill when the decisive path runs through an Android app's live trust boundary rather than static strings alone.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Preserve the original APK, extracted resources, and decompiled output before patching or resigning.
122. Start with manifest, exported components, deeplinks, native libs, prefs, local DBs, and bundled configs.
133. Decide the narrowest runtime boundary to hook: signer, crypto helper, JNI bridge, WebView bridge, or request builder.
144. Correlate static evidence and dynamic traces before claiming a trust edge is understood.
155. Reproduce the signed request, accepted token, or gated branch from the smallest hook set.
16 
17## Workflow
18 
19### 1. Static Triage Before Hooks
20 
21- Map package structure, exported activities, services, receivers, providers, and deeplink handlers.
22- Note SSL pinning logic, root checks, feature flags, token storage, shared prefs, SQLite tables, and protobuf or RPC boundaries.
23- Identify whether the sensitive logic sits in Java, Kotlin, JNI, or a bundled WebView.
24 
25### 2. Hook The Narrowest Boundary
26…