competition-reverse-pwnlisted

# Competition Reverse Pwn 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 for binary-heavy challenges where the decisive path runs through artifacts, decoded layers, process behavior, crash state, or exploit primitives. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Preserve the original artifact before unpacking, patching, or instrumenting. 2. Start with passive triage: type, headers, sections, imports, strings, entropy, resources. 3. Decide whether the path is reverse-first, DFIR-first, or exploit-first. 4. Tie every claim to an observable boundary: decode edge, persistence edge, crash edge, or leak edge. 5. Reproduce the artifact or primitive from a clean baseline. ## Workflow ### 1. Reverse Or Forensic Triage - Separate loader, payload, config, and post-decode behavior. - Correlate files, memory, logs, registry, services, tasks, IPC, and PCAPs as one graph. - Keep decoded or dumped artifacts separate from the pristine sample. ### 2. Native And Exploit Path - Map mitigations, loader behavior, libc or runtime, syscall and IPC surfaces, and protocol framing. - Record the primitive, controllable bytes, leak source, target object, and final artifact separately. - Compare host, libc, loader, and framin