competition-crypto-mobile

1# Competition Crypto Mobile
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 active challenge depends on recovering a transform chain, hidden media payload, mobile signing path, or local trust boundary.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Decide whether the dominant path is crypto, stego, or mobile.
122. Recover transforms in order; do not jump straight to the fanciest algorithm.
133. Record exact parameters and boundaries that affect the result.
144. Hook the narrowest mobile boundary that proves the behavior.
155. Reproduce the plaintext, payload, signed request, or accepted branch.
16 
17## Workflow
18 
19### 1. Crypto And Encoding
20 
21- Reconstruct the chain step by step: container, compression, encoding, xor or substitution, crypto, integrity, final parse.
22- Keep exact keys, IVs, nonces, salts, tags, offsets, and byte order.
23 
24### 2. Stego
25 
26- Inspect metadata, chunk layout, palettes, alpha planes, LSBs, thumbnails, trailers, and transcoding artifacts.
27- Rank decode attempts by evidence, not by brute-force curiosity.
28 
29### 3. Mobile
30 
31- Start with manifest or plist, exported components, deeplinks, native libs, shared prefs, local DBs, and configs.
32…