Competition ZIP Archive is a downstream skill of ctf-sandbox-orchestrator for encrypted ZIP and PKZIP challenges. It prefers the legacy ZipCrypto known-plaintext route when a challenge supplies a predictable file, header or template, and avoids starting with blind password guessing.
The skill preserves the original archive, confirms the real encryption mode, builds a matching plaintext fixture, recovers internal keys with bkcrack and validates the unlocked copy. A reference table says when to re-route to the upload parser, stego or crypto skills. Replies are in Simplified Chinese unless English is requested.
What You Get
- A four-stage workflow from archive inspection to validated extraction
- A decision table that maps observations such as stored or deflated entries and modern encryption to the next step
- Tool setup notes that use the repository’s tool index and a pinned bkcrack capability
- An evidence checklist covering hashes, entry names, plaintext source, key recovery output and final artifact validation
Common Use Cases
- Solving an encrypted ZIP in a CTF where a template, file header or config file is predictable
- Checking whether an archive uses legacy ZipCrypto before choosing an approach
- Documenting a key recovery with hashes and commands so it can be reproduced
- Deciding when to hand the archive to the file parser, stego or crypto skills
What Makes It Unique
It is narrow and careful about preconditions. It explains that a ZIP local header is metadata and not useful plaintext, that a deflated entry needs matching compressed bytes, and that recovered keys are internal keys and not the password. Those details keep the known-plaintext path from failing in ways that look like tool errors.
Under The Hood
The skill is a markdown workflow with one reference file and an agent metadata file. It ships no scripts of its own but names shell and PowerShell commands: hashing, file, bkcrack and 7z, plus the repository’s refresh-tool-index and bootstrap scripts, which install bkcrack from a pinned GitHub release and check the asset digest. The agent therefore runs commands, may download that release, and writes working copies, unlocked archives and extracted files under the analysis project’s work folder. The original archive is kept unchanged. It applies only after the orchestrator has set sandbox assumptions.