Individual skill

malware-analyst

Analyze suspicious files safely with static and dynamic techniques to determine capability, indicators, and defensive mitigations.

skills/malware-analyst/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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)
56
Repository last updated
Oct 10, 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

## Overview

Malware analysis answers: **what does this file do, how do we detect it, and how do we stop it?** Analysts work in isolated labs, using static analysis (examining the file without running it) and dynamic analysis (observing it in a sandbox) to extract indicators of compromise (IOCs) and behaviors defenders can detect and block.

This skill is strictly defensive: safe handling, analysis methodology, IOC extraction, and turning findings into detections. It contains no instructions for creating, modifying, or weaponizing malware.

Malware analysis is detective work where the evidence actively lies to you — packers, anti-analysis tricks, and environment checks all exist to waste your time. Methodology is the countermeasure: static before dynamic, hypotheses before conclusions, and every claim backed by an artifact. The analyst's real product is not the report but the detections and hunts it enables.

## When to use

- Triaging a suspicious attachment, download, or endpoint detection.
- Enriching an incident with IOCs (hashes, domains, IPs, mutexes, registry keys).
- Writing detections for a malware family or campaign.
- Deciding whether an alert is a true infection or a false positive.
Back to top