1---2name: malware-reverse-engineering3description: 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.4metadata:5 source: https://skillmd.com/skills/masriyan/malware-reverse-engineering6---78# Malware Reverse Engineering910## Safety Boundary1112- Treat samples as hostile. Use isolated labs, snapshots, no shared clipboard, no mounted personal directories, and controlled networking.13- Do not provide malware improvement, persistence, stealth, evasion, credential theft, or deployment guidance.14- Focus on behavior, indicators, detection, containment, and eradication.1516## Workflow17181. Record sample metadata: filename, hashes, size, type, source, timestamp, and handling notes.192. Perform static triage: strings, imports, sections, packer hints, scripts/macros, config blobs, and suspicious capabilities.203. Plan dynamic analysis with containment: VM snapshot, fake services, monitored filesystem/registry/process/network activity.214. Summarize behavior by capability: execution, persistence, privilege, defense evasion, discovery, C2, collection, exfiltration.225. Produce IOCs, detection logic ideas, remediation steps, and confidence levels.2324## Output Format2526- `Summary`: what the artifact appears to do.27- `Evidence`: strings, APIs, paths, domains, mutexes, commands, or observed events.28- `IOCs`: hashes, filenames, registry keys, network indicators, and caveats.29- `Detections`: YARA/Sigma/EDR hunting ideas where appropriate.30- `Response`: containment, eradication, recovery, and monitoring.31