Analyzing rat command and control
Skill meltedinhex/analyst-ai-pack/skills/analyzing-rat-command-and-control
An open agent-skills library for malware analysis, reverse engineering, and threat hunting - 118 curated, runnable skills mapped to MITRE ATT&CK, D3FEND, and CAR.
npx -y skills add meltedinhex/analyst-ai-pack --skill analyzing-rat-command-and-controlAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Analyzes remote access trojan command-and-control by mapping the RAT command set, identifying the C2 transport and beacon parameters, and cataloging operator capabilities from static strings and config. Activates for requests to analyze RAT C2, map a trojan command handler, or identify remote-access capabilities and C2 transport.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.6 KB, as published. Nobody here has run it
Analyzing RAT Command and Control
When to Use
- You have a RAT sample and need to map its command set (shell, file ops, screenshot, keylog, webcam, proxy), C2 transport, and beacon parameters.
- You are cataloging operator capabilities for detection and impact assessment.
Do not use this to operate the RAT or connect to its C2 — characterize capabilities from inert static analysis.
Prerequisites
- The RAT sample (read inertly), optionally with an extracted config.
Safety & Handling
- Read bytes statically; defang C2 endpoints; never connect to the C2.
Workflow
Step 1: Map command handlers and capabilities
python scripts/analyst.py profile sample.bin
Matches command-keyword and API patterns for capability classes: remote shell, file transfer, screenshot/keylog/webcam, persistence, proxy/relay, and self-update.
Step 2: Identify the C2 transport
Detect HTTP(S), raw TCP, TLS, DNS, or messaging-platform transport from imports/strings, plus beacon intervals/user-agents where present.
Step 3: Build the capability matrix
Summarize capabilities and transport, mapping to ATT&CK.
Step 4: Defang and report
Defang endpoints and produce IOCs.
Validation
- Capabilities are grouped into classes with the matched evidence.
- The C2 transport is identified from concrete imports/strings.
- Findings map to ATT&CK T1219/T1071.
Pitfalls
- Generic API presence (e.g.,
gdi32) misread as screenshot capability — corroborate with command handlers. - Commodity RAT builders sharing strings across families — avoid over-attribution.
- Encrypted command sets requiring config decryption first.
References
- See
references/api-reference.mdfor the profiler. - ATT&CK T1219 and T1071 (linked in frontmatter).