competition-dpapi-credential-chainlisted

# Competition Dpapi Credential Chain 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 Windows secret is DPAPI-protected and the hard part is proving which context unwraps it and where the plaintext is accepted. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Separate protected blob, masterkey, decrypting context, and final accepting service. 2. Record SID, user or machine context, masterkey path, vault or browser store, and target replay point before broad conclusions. 3. Keep DPAPI source artifact, unwrap step, plaintext secret, and acceptance edge in one chain. 4. Distinguish local user DPAPI, machine DPAPI, domain backup key use, and application-specific wrapping. 5. Reproduce the smallest DPAPI-to-accepted-access path that proves the decisive edge. ## Workflow ### 1. Map Protected Secret And DPAPI Context - Record blob source, masterkey location, SID, protector scope, profile path, credential store, and any application wrapper such as browser encryption or vault metadata. - Note whether the decisive value lives in Credential Manager, Vault, browser cookies, browser passwords, Wi-Fi profiles, RDP files, or custom app storage. - Keep protected artifact, masterkey candidate, and accoun