Competition iOS Runtime

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 live iOS trust boundaries rather than static strings or plist values alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

1. Preserve the original IPA, extracted bundle, and any decrypted or re-signed copy as separate artifacts.
2. Start with Info.plist, entitlements, URL schemes, frameworks, Keychain usage, and local app storage before broad runtime hooks.
3. Choose the narrowest runtime boundary that proves behavior: signer, trust evaluator, Keychain accessor, Objective-C or Swift method, or network request builder.
4. Correlate static bundle evidence and live hook output before claiming the trust path is understood.
5. Reproduce the accepted request, token, or gated branch from the smallest hook set.

Workflow

1. Static iOS Triage

• Map bundle structure, Info.plist, entitlements, URL schemes, universal links, embedded frameworks, and app group paths.
• Record likely trust boundaries: request signers, device binding, certificate checks, jailbreak checks, Keychain access, or local cache loading.
• Note whether sensitive logic sits in Objective-C, Swift, embedded frameworks, or a bundled web surface.

2. Hook The Runtime Boundary

• Prefer hooking request builders, crypto helpers, trust evaluators, Keychain reads, or Objective-C selectors instead of broad UI handlers.
• Record plaintext inputs, headers, nonces, signed strings, and outputs at the boundary that changes server acceptance.
• Patch or bypass pinning or environment checks only enough to expose the real request path.

3. Replay The Accepted Path