Menu

Individual skill

reverse-eng-malware

0upvotes

Fully analyze a malware sample — static, dynamic, and behavioral — including unpacking and IAT rebuild, import-table triage, anti-analysis detection and defeat, IOC extraction, and YARA/Sigma rule writing. Load when handed a suspicious PE/ELF/Mach-O/script sample to reverse beyond quick triage: packed binaries, "analyze this malware", a sandbox run that shows no behavior, or a need for durable detection. Signals: a dropped sample, a VirusTotal/MalwareBazaar hash, C2 strings, anti-VM/anti-debug checks, "write a YARA rule for this family".

skills/reverse-engineering/reverse-eng-malware/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Oct 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Malware analysis (deep RE)

## When it applies
`defense-malware-triage` gave a verdict and you need the deep dive: a packed or obfuscated sample, a
family you must write durable detection for, or an implant recovered on an engagement whose C2,
injection, and persistence mechanisms you need to document. Covers EXE / DLL / SYS / .NET and script
droppers (bat, ps1, vba). Always work inside an isolated analysis VM — detonating an unknown sample
on a real host is itself an incident.

## Why it works
Malware hides its intent behind packing, dynamic API resolution, and environment checks, but every
layer must eventually resolve to real API calls and real behavior. Static analysis maps the
capabilities; a debugger or sandbox catches what only exists at runtime (decrypted strings, resolved
imports, injected code). Detection written on code/string internals — not hashes — survives
Back to top