Competition Windows Pivot is a downstream skill of ctf-sandbox-orchestrator for CTF challenges where progress depends on moving between Windows hosts. It organizes the work as a chain: foothold, recovered artifact, replay path, pivot host and resulting capability.
The skill separates stored credential material from usable privilege, keeps host evidence and ticket evidence on one timeline, and records which service accepted each artifact. It is written for sandbox and lab environments set up by the orchestrator, and replies in Simplified Chinese unless English is requested.
What You Get
- A three-part workflow: recover the replay material, trace the pivot chain, report the edge
- A Kerberos evidence block listing ticket type, SPN, delegation mode, PAC data, encryption type, cache location and accepting service
- A host evidence list of event IDs, logon IDs, process, service and task creation, and token or group changes
- Pointers to four narrower skills for DPAPI, LSASS ticket material, delegation and relay or coercion
Common Use Cases
- Writing up how a CTF lab chain moved from one Windows host to another
- Proving which service accepted a ticket or credential in a training domain
- Separating possession of a ticket from accepted privilege when reviewing a lab result
- Keeping raw host artifacts apart from the derived timeline in a report
What Makes It Unique
It insists on a destination-side effect. A pivot counts only when the report shows what crossed which boundary and what capability appeared on the target host, and its pitfalls list warns against treating a ticket in hand as proof of privilege. It also acts as a router to the DPAPI, LSASS, delegation and relay skills in the same package.
Under The Hood
The skill is a markdown workflow with one reference checklist and an agent metadata file. It ships no scripts. The instructions direct the agent to inspect host artifacts and logs of the sandbox machines and to follow remote-service traffic, so the agent may run shell or PowerShell commands and open network connections to lab hosts. The skill names credential stores as things to inspect and does not carry commands for extracting them. It applies only after the orchestrator has set sandbox assumptions.