Competition Malware Config is a downstream skill of the CTF Sandbox Orchestrator. It covers configuration recovery, staged payload boundaries, beacon parameter extraction and IOC decoding for samples handled in a sandbox.
The agent preserves the original sample, separates loader, payload, config blob and post-decode behavior, and records the exact transform chain for each recovered field. Decoded fields are then matched to the branch or protocol step each one influences.
What You Get
- A quick start that preserves the original sample before any unpacking
- A three-stage workflow: find the config boundary, reconstruct the decode chain, tie config to behavior
- A rule to keep original, unpacked, dumped and parsed outputs as separate artifacts
- A list of fields to relate to behavior, from beacon path to campaign ID
- Guidance to correlate decoded config with PCAPs, process trees or stage2 strings
Common Use Cases
- Decoding C2 and beacon parameters of a challenge sample
- Extracting a bot or campaign ID from a staged payload
- Documenting offsets, keys and masks of a decode chain
- Linking a decoded mutex or persistence name to observed process behavior
What Makes It Unique
It asks which fields a sample hides and when they become plaintext, and not only what the sample does. All fields from one decode chain are grouped, which stops unrelated clues from being mixed into a false config.
Under The Hood
The skill is instruction text only: the SKILL.md body, one reference checklist and a small agent config file that disables implicit invocation. It ships no scripts and no decoders. The instructions tell the agent to inspect a sample the user supplies inside a sandbox, which means the agent would run analysis and unpacking tools itself. The skill replies in Simplified Chinese unless asked for English and runs only after the orchestrator skill is active.