zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-zip-archive
competition-zip-archive
VerifiedInternal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for ZIP and PKZIP archive challenges, legacy ZipCrypto identification, known-plaintext recovery with bkcrack, key-based decryption, and reproducible extraction. Use when the user asks to solve an encrypted ZIP challenge, inspect ZipCrypto metadata, recover keys from a known file prefix, or unlock an archive without starting with password brute force. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.7 KB |
| agents/openai.yaml | config | 413 B |
| references/zip-archive.md | markdown | 2.9 KB |
references/zip-archive.md
View on GitHub# ZIP Archive Challenge Reference
## Route Decision
| Observation | Next step |
|---|---|
| ZIP/PKZIP archive, legacy encryption, predictable member bytes | Use `bkcrack` known-plaintext recovery |
| Entry is stored and its file format is known | Build a matching plaintext fixture and attack the entry |
| Entry is deflated | Match the compressed entry bytes; do not pass an unrelated uncompressed file |
| WinZip AES or another modern encryption mode | `bkcrack` is not the right primitive; re-route |
| Upload reaches an application parser or extractor | Use `competition-file-parser-chain` |
| Archive is only a carrier for hidden media data | Use `competition-stego-media` |
## Minimal Inspection
```text
file challenge.zip
bkcrack -L challenge.zip
7z l -slt challenge.zip
```
Record the entry name, compression method, encrypted flag, compressed size, uncompressed size, CRC, and any duplicate entries. The ZIP local-file and central-directory signatures are archive metadata; seeing `PK` in the container does not disclose the plaintext of an encrypted member.
## Known-Plaintext Requirements
Legacy ZipCrypto key recovery needs at least 12 known plaintext bytes. At least 8 bytes should be contiguous; more contiguous bytes improve speed and reliability. Good sources include:
- a challenge-provided template or source file;
- a predictable file signature plus enough fixed header bytes;
- a known serialized structure with stable fields;
- a second entry encrypted with the same password and a known exact representation.
For compressed entries, the bytes must correspond to the encrypted data representation. A plaintext ZIP fixture is useful because `bkcrack -P`/`-p` lets the tool read the matching entry representation.
## Command Forms
Archive entry to archive entry:
```bash
bkcrack -C encrypted.zip -c cipher -P plain.zip -p plain
```
Raw files, with an offset or sparse bytes when justified by evidence:
```bash
bkcrack -c cipherfile -p plainfile -o offset
bkcrack -c cipherfile -p plainfile -x 25 4b4f -x 30 21
```
Decrypt every compatible entry after key recovery:
```bash
bkcrack -C encrypted.zip -k 12345678 23456789 34567890 -D unlocked.zip
```
Decrypt one raw member:
```bash
bkcrack -c cipherfile -k 12345678 23456789 34567890 -d decipheredfile
```
Do not publish a command with placeholder keys as if it were a successful solve. Replace them with the values from the actual recovery output and record the source evidence.
## Evidence Checklist
- [ ] Original archive hash recorded before any extraction
- [ ] Archive type and encryption mode confirmed
- [ ] Entry name and compression method recorded
- [ ] Known plaintext bytes and their source explained
- [ ] At least 12 known bytes, including 8 contiguous bytes, or justified sparse offsets
- [ ] Key recovery output saved
- [ ] Decrypted archive tested and extracted from a new path
- [ ] Final artifact or flag independently validated
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |