Skip to content

zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-malware-config

competition-malware-config

Verified

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.

FileKindSize
SKILL.mdskill md2.7 KB
agents/openai.yamlconfig376 B
references/malware-config.mdmarkdown1.2 KB

references/malware-config.md

View on GitHub
# Malware Config And Staging Checklist

## Hunt For The Config Boundary

- Resources, overlays, embedded archives, section anomalies, decode helpers, registry seeds, bootstrap responses, stage2 memory
- Nearby markers: URLs, mutex seeds, wallet-like strings, campaign IDs, bot IDs, task routes, persistence names

## Reconstruct The Transform Chain

Track in order:

1. Container or embedded layer
2. Compression or chunking
3. Encoding or substitution
4. XOR or custom masks
5. Crypto
6. Final parse into fields

## Tie Fields To Behavior

- Beacon path or host -> network flow
- Mutex or install path -> persistence branch
- Campaign or bot id -> server-side routing or tasking
- Wallet or key material -> downstream protocol or decryption branch

## Evidence To Keep

- One compact block for offsets, hashes, decode helpers, keys, masks
- One compact block for parsed fields and what branch each field affects
- Original, unpacked, dumped, and parsed outputs kept as separate artifacts

## Common Pitfalls

- Treating one IOC-looking string as the config without proving the full chain
- Mixing fields from separate decode paths as if they came from one blob
- Forgetting to prove where config becomes plaintext
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall