competition-malware-config

Recover malware configuration fields, staged payloads, and beacon parameters under sandbox assumptions.

21|8|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill competition-malware-config-chengzongcai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: competition-malware-config
Source: https://github.com/chengzongcai/reverse-skill-backup/tree/main/CTF-Sandbox-Orchestrator/competition-malware-config
Command: npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill competition-malware-config-chengzongcai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When analyzing a malware sample in a CTF or sandbox setting, the decisive value is often not just what the sample does but which config fields, staging layers, and network parameters it hides. This Skill provides a repeatable workflow for locating the config boundary, reconstructing the decode chain, and tying recovered fields to observed behavior. ## Core Features & Use Cases - Config Boundary Discovery: Locate where configuration is stored, whether in resources, overlays, encrypted blobs, registry seeds, bootstrap responses, or stage2 memory. - Decode Chain Reconstruction: Recover the full transform chain in order (container, compression, encoding, XOR or substitution, crypto, final parse) and group fields from the same chain together. - Behavior Correlation: Map each recovered field (beacon path, mutex, bot ID, campaign ID, wallet, persistence name) to the branch or protocol step it actually influences. - Use Case: Given a packed sample with an encrypted config blob, use this Skill to rank candidate blobs by entropy and nearby strings, recover the XOR key and decode helpers, and produce a compact evidence block of offsets, hashes, keys, and parsed fields. ## Quick Start After the ctf-sandbox-orchestrator skill is active, ask it to recover the hidden config, staging layers, bot IDs, or beacon parameters from the current sample.

Frequently Asked Questions about competition-malware-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recover a malware config from a packed sample?▼

Start by locating the config boundary in resources, overlays, embedded archives, or stage2 memory. Then reconstruct the decode chain in order: container, compression, encoding, XOR or substitution, crypto, and final parse, preserving keys, offsets, and hashes as evidence.

How to extract beacon parameters and C2 fields from malware?▼

Rank candidate config blobs by entropy, field shape, nearby strings, and decode helpers, then decode them through the recovered transform chain. Tie each extracted field, such as beacon path, bot ID, or campaign ID, to the network flow or branch it influences.

Can I use this skill without ctf-sandbox-orchestrator?▼

No. This is an internal downstream skill that requires ctf-sandbox-orchestrator to be active first, since it relies on established sandbox assumptions, node ownership, and evidence priorities before routing here.

What evidence should be preserved during malware config analysis?▼

Keep the original artifact, unpacked layer, dumped stage, and parsed config as separate artifacts. Record offsets, hashes, decode helpers, keys, masks, and field names in one compact block, plus a second block mapping each field to the branch it affects.

Why does malware config extraction fail on some samples?▼

Common pitfalls include treating a single IOC-looking string as the full config without proving the decode chain, mixing fields from separate decode paths, and failing to prove where the config becomes plaintext. Verify the complete transform chain before trusting recovered fields.