malware-reverse-engineering
Skill1 starsChanged 3 months agoMITView on GitHub
Malware reverse engineering and suspicious artifact analysis skill for defensive triage, static analysis, dynamic analysis planning, unpacking strategy, indicators of compromise, behavior summaries, YARA/Sigma ideas, and remediation guidance. Use for suspicious binaries, scripts, documents, logs, memory artifacts, sandbox reports, and malware family analysis in isolated environments.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Masriyan/gemini-security-skillsword for word, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Masriyan/gemini-security-skills★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- kubernetes-securitySkill
- multilingualSkill
- offensive-securitySkill
- osint-recon-automationSkill
- prompt-enhancementSkill
- purple-team-automationSkill
- python-programmingSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Treat samples as hostile. Use isolated labs, snapshots, no shared clipboard, no mounted personal directories, and controlled networking.
- Distinctive: line 11
Do not provide malware improvement, persistence, stealth, evasion, credential theft, or deployment guidance.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Malware Reverse Engineering
Safety Boundary
- Treat samples as hostile. Use isolated labs, snapshots, no shared clipboard, no mounted personal directories, and controlled networking.
- Do not provide malware improvement, persistence, stealth, evasion, credential theft, or deployment guidance.
- Focus on behavior, indicators, detection, containment, and eradication.
Workflow
- Record sample metadata: filename, hashes, size, type, source, timestamp, and handling notes.
- Perform static triage: strings, imports, sections, packer hints, scripts/macros, config blobs, and suspicious capabilities.
- Plan dynamic analysis with containment: VM snapshot, fake services, monitored filesystem/registry/process/network activity.
- Summarize behavior by capability: execution, persistence, privilege, defense evasion, discovery, C2, collection, exfiltration.
- Produce IOCs, detection logic ideas, remediation steps, and confidence levels.
Output Format
Summary: what the artifact appears to do.Evidence: strings, APIs, paths, domains, mutexes, commands, or observed events.IOCs: hashes, filenames, registry keys, network indicators, and caveats.Detections: YARA/Sigma/EDR hunting ideas where appropriate.Response: containment, eradication, recovery, and monitoring.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.