CTF-Sandbox-Orchestrator/competition-dpapi-credential-chain/SKILL.md·查看原始 Markdown·索引

name: competition-dpapi-credential-chain description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for DPAPI masterkeys, vault blobs, browser credential stores, protected secrets, domain backup keys, and secret-to-acceptance replay chains. Use when the user asks to inspect DPAPI blobs or masterkeys, recover browser or vault credentials, trace DPAPI context or backup-key use, or explain how protected Windows secrets become accepted access or privilege. Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions and routed here.


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

2. Prove Unwrap And Acceptance

3. Reduce To The Decisive DPAPI Chain

Read This Reference

What To Preserve