competition-malware-config — Claude Code skill: what it does
competition-malware-config — a skill for Claude Code and other platforms recovers malware configurations, decodes C2 beacon parameters, and extracts IOCs.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-malware-config -a claude-codeWhat competition-malware-config does
The skill runs as a downstream specialization after $ctf-sandbox-orchestrator establishes sandbox assumptions. It processes suspicious binaries to locate config boundaries, separate staged loaders, and reconstruct the full decode chain.
Original artifacts are preserved while entropy and field shapes are analyzed. Decoded parameters are tied directly to protocol behavior like mutexes, wallets, and beacon paths.
What it helps with
- recover malware configuration blobs
- decode C2 and beacon parameters
- unpack staged payloads
- reconstruct container decode chains
Example prompts for the agent
- Recover the malware config and decode the C2 fields
- Unpack the staged payload and extract beacon parameters
- Trace the config decode chain for this sample
How to install competition-malware-config
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-malware-config -a claude-code2Manually: put the files in place
~/.claude/skills/competition-malware-config/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-malware-config/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-malware-config -a codex2Manually: put the files in place
.agents/skills/competition-malware-config/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-malware-config -a cursor2Manually: put the files in place
.cursor/skills/competition-malware-config/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-malware-config/SKILL.md2Manually: put the files in place
.github/skills/competition-malware-config/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-malware-config -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-malware-configManually: put the files in place
.devin/skills/competition-malware-config/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-malware-config -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-malware-config
How to install competition-malware-config in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-malware-config -a claude-code and verify ~/.claude/skills/competition-malware-config/SKILL.md.
What does competition-malware-config do?
It automates malware configuration recovery, staged payload unpacking, and beacon parameter extraction under sandbox orchestration.
What is needed to run competition-malware-config?
An active $ctf-sandbox-orchestrator instance must establish sandbox assumptions before this skill runs.
Source text
SKILL.md · MIT
--- name: competition-malware-config description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for malware configuration recovery, staged payload boundaries, beacon parameter extraction, and IOC decoding. Use when the user asks to recover a malware config, decode C2 or beacon fields, unpack staged payloads, extract bot or campaign IDs, or tie recovered config to observed protocol behavior under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Malware Config 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 value is not just "what the sample does," but which config fields, stages, or network parameters the sample hides and when they become plaintext. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Preserve the original sample before unpacking or patching. 2. Separate loader, payload, config blob, and post-decode behavior. 3. Rank candidate config blobs by entropy, field shape, nearby strings, and decode helpers. 4. Record the exact transform chain for each recovered field. 5. Reproduce the decoded config or beacon parameters from the smallest possible path. ## Workflow ### 1. Find The Config Boundary - Inspect sections, resources, embedded archives, strings, imports, and decode helpers. - Identify where config is stored: resource, overlay, encrypted blob, registry seed, network bootstrap, or stage2 memory. - Keep one note of when each value becomes plaintext. ### 2. Reconstruct The Decode Chain - Recover the chain in order: container -> compression -> encoding -> xor/substitution -> crypto -> parse. - Group all config fields from the same chain together instead of treating them as unrelated clues. - Preserve hashes, offsets, keys, IVs, masks, and parsed fields in one compact evidence block. ### 3. Tie Config To Behavior - Show which field affects which branch: beacon path, mutex, wallet, bot id, campaign, tasking route, persistence name, or process target. - Correlate decoded config with PCAPs, process trees, or stage2 strings when possible. ## Read This Reference - Load `references/malware-config.md` for the config-hunting checklist, staged-sample checklist, and evidence packaging rules. ## What To Preserve - Original artifact, unpacked layer, dumped stage, and parsed config as separate artifacts - Offsets, hashes, decode helpers, keys, masks, and field names - The branch or protocol step each recovered field actually influences
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill