Skip to content
cccskills
FreePublished on GitHub

competition-malware-config

Recover hidden malware settings and communication parameters in an isolated CTF environment. Document how values are decoded, preserve supporting evidence, and connect recovered fields to the sample’s observed behavior.

OriginalShow the original 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.

See how to install

Good for

  • Recovering hidden malware configuration fields
  • Decoding command server addresses and beacon settings
  • Separating loaders from staged payloads
  • Connecting recovered settings to network behavior

Files included (3)

  • SKILL.md2.7 KB
  • agents/openai.yaml376 B
  • references/malware-config.md1.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

api-security

FreeSummary

Assess authorized APIs through a ten-stage workflow covering endpoint discovery, authentication, access permissions, input handling, and request limits. Collect reproducible evidence and turn findings into regression checks that can run in a development pipeline.

  • Review API authentication and access permissions
  • Assess GraphQL and WebSocket security
  • Check request limits and unintended data exposure
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

apk-reverse

FreeSummary

Inspect Android APKs from the command line to understand app logic, permissions, and components. Supports Java decompilation, low-level code edits, rebuilding and signing, plus Frida observation of running methods and routing to native code analysis.

  • Inspecting APK entry points, components, and permissions
  • Locating login, signing, and certificate checks
  • Editing smali code and rebuilding an APK
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

attack-chain

FreeSummary

Plan and coordinate authorized penetration tests across multiple stages, from reconnaissance to access, privilege escalation, movement between systems, and impact assessment. Assign specialist skills, revise blocked paths, and maintain evidence and progress records for the final report.

  • Plan a penetration test across multiple stages
  • Assess how far a vulnerability could lead
  • Replan from existing credentials or system access
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

binary-diff

FreeSummary

Transfer known function and variable names from an older binary to a newer version. Compare disassembly and pseudocode with an LLM, produce structured mappings, and apply names and comments in IDA.

  • Migrate known function names after a software update
  • Locate kernel functions when the new PDB is unavailable
  • Find updated function addresses and structure offsets
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

Inspect compiled programs in Binary Ninja using strings, function references, and intermediate representations—views of program logic at different levels. Trace data flow and report findings with addresses, supporting evidence, confidence, and reproduction steps.

  • Tracing function calls and data flow in Binary Ninja
  • Cross-checking findings from other disassemblers
  • Automating binary analysis with the Python API
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

Automate website navigation, form filling, content collection, and Windows desktop interactions. The skill selects browser or desktop tools for the task and guides screenshot capture and desktop network traffic observation when needed.

  • Automating website login and form entry
  • Collecting page content and screenshots
  • Operating Windows desktop applications
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

See all skills by zhaoxuya520

Report a problem with this skill