competition-android-hooking

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use 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.

Use this skill when the decisive path runs through an Android app's live trust boundary rather than static strings alone.

Reply in Simplified Chinese unless the user explicitly requests English.

仅当

$ctf-sandbox-orchestrator

已激活，且已完成沙箱环境假设、节点归属确认和证据优先级划分后，才可作为下游专项技能使用。如果尚未完成上述步骤，请先返回

$ctf-sandbox-orchestrator

执行前置流程。

当问题的核心解决路径需要分析Android应用的运行态信任边界，而非仅依赖静态字符串时使用本技能。

除非用户明确要求使用英文回复，否则请使用简体中文回复。

Preserve the original APK, extracted resources, and decompiled output before patching or resigning.
Start with manifest, exported components, deeplinks, native libs, prefs, local DBs, and bundled configs.
Decide the narrowest runtime boundary to hook: signer, crypto helper, JNI bridge, WebView bridge, or request builder.
Correlate static evidence and dynamic traces before claiming a trust edge is understood.
Reproduce the signed request, accepted token, or gated branch from the smallest hook set.

Map package structure, exported activities, services, receivers, providers, and deeplink handlers.
Note SSL pinning logic, root checks, feature flags, token storage, shared prefs, SQLite tables, and protobuf or RPC boundaries.
Identify whether the sensitive logic sits in Java, Kotlin, JNI, or a bundled WebView.

梳理包结构、导出的Activity、Service、Receiver、Provider和deeplink处理逻辑。
标记SSL pinning逻辑、root检测、功能开关、token存储位置、Shared Preferences、SQLite表、protobuf或RPC边界。
识别敏感逻辑所处的层：Java、Kotlin、JNI还是内置WebView。

Prefer hooking request signers, crypto helpers, keystore access, protobuf encode or decode, or JNI marshaling instead of broad UI hooks.
Record plaintext inputs, signed strings, headers, nonces, and outputs at the boundary that actually changes trust.
If pinning or environment checks block progress, patch or hook only enough to expose the real request path.

Rebuild the smallest sequence that reaches the accepted server-side branch: local state, nonce, request body, signature, and headers.
Keep hook logs, captured request shapes, and local storage paths tied to the same account or session state.
If the challenge becomes more about transform recovery than Android runtime, switch back to the broader crypto or mobile skill.

Load
```
references/android-hooking.md
```
for hook targets, storage checklist, and evidence packaging.

Hook points, class names, JNI symbols, signer inputs and outputs, and header names
Shared prefs, local DB rows, deeplinks, exported components, and token storage paths
The smallest replayable request or branch that proves the trust boundary