analyzing-malware

analyzing-malware is a skill for Claude Code from trilwu/secskills. It costs 69 tokens per session (3,586 once invoked), scanned A, original, MIT.

A guide for safely examining suspected malicious files, scripts, or other samples. It covers both looking at the sample without running it and running it in an isolated environment.

In plain words
What is it for?
It helps determine what a sample does, find persistence and command-and-control behaviour, extract indicators for searches and blocking, and create YARA or behaviour-based detections.
Why use it?
Malware analysis can infect the analyst’s machine or expose an investigation unless the sample is contained and its findings are handled carefully.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is yara -w rule.yar ./samples/family/ # must hit all known-true samples.

Part of the secskills-defense plugin — 22 skills shipped together

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/trilwu/secskills
agentmods
npx agentmods add skills/trilwu/secskills/analyzing-malware

Made for: Claude Code.

Or install secskills-defense, the plugin that ships this one along with the rest of its 22 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for analyzing-malware

README.md
[![agentmods](https://agentmods.dev/badge/skills/trilwu/secskills/analyzing-malware.svg)](https://agentmods.dev/skills/trilwu/secskills/analyzing-malware)
Your own site
<a href="https://agentmods.dev/skills/trilwu/secskills/analyzing-malware"><img src="https://agentmods.dev/badge/skills/trilwu/secskills/analyzing-malware.svg" alt="Measured on agentmods" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,586 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00069 $0.03586
Opus 5 $0.00034 $0.01793
Sonnet 5 $0.00014 $0.00717
Haiku 4.5 $0.00007 $0.00359

Measured 6d ago against content hash 3f463bc9fd4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

analyzing-malware scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sL "https://defuddle.md/<url>" # scheme in the path is optional
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

secskills-defense/skills/analyzing-malware/SKILL.md · 317 lines

How it starts

The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyzing Malware

The analysis is the easy part. The part that goes wrong is containment: a sample detonated on a machine that can reach production, or an IOC published that burns an active investigation. Get the environment right first.

When to Use

  • Triaging a suspicious file, attachment, script, or dropped binary
  • Determining a sample's capability, persistence, and command-and-control
  • Extracting indicators for hunting and blocking
  • Writing YARA or behavioural detection from a specimen
  • Supporting an incident with sample-derived intelligence

When NOT to Use

  • Writing malware, droppers, loaders, or evasion code — out of scope for this skill regardless of framing
  • Pure RE of a benign binary — use analyzing-binaries
  • A raw shellcode blob with no PE/ELF header — use analyzing-shellcode
  • The sample's network capture — use analyzing-network-traffic
  • Sweeping a whole web source tree for planted webshells (not one recovered sample) — use hunting-web-backdoors
  • Writing a YARA signature for the family — use writing-yara-rules
  • The wider incident — use responding-to-incidents
  • Turning findings into deployed rules — use engineering-detections
  • Pivoting sample IOCs into related infrastructure, actor tracking, or a finished intel product — use producing-threat-intelligence

Containment: Do This Before Anything Else

Control Requirement
Host Disposable VM or dedicated bare-metal, snapshot taken before execution
Network Isolated segment; simulated services (INetSim/FakeNet-NG) by default
Shares No host folder sharing, no clipboard sharing, no mounted host drives
Credentials No real accounts, no domain join, no password manager
Handling Sample stored in a password-protected archive, extension neutered (.bin, .mal)
Egress Real internet only with an explicit decision and a plan for attribution leakage

Live C2 contact tells the operator you are looking. On an active incident, do not resolve the C2 domain, submit the hash publicly, or upload the sample to a multi-scanner service until the incident lead approves it — public submission is a disclosure.

Read the full file on GitHub · 317 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 317 lines · 69 tokens per session scan A 3f463bc9fd4e

Subscribe to this mod's changes

analyzing-malware is a skill published in the GitHub repository trilwu/secskills (135 stars, last pushed 2d ago), licensed MIT. It adds 69 tokens to every session and 3,586 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

claude-md-improver

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…

anthropics/claude-plugins-official · 82 tokens

agent-platform-rag-engine-management

Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…

google/skills · 85 tokens

gke-reliability

Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).

google/skills · 73 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…

google/skills · 181 tokens

agent-platform-model-registry

Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.

google/skills · 60 tokens

google-cloud-solution-agentic-analytics-spark-knowledge-catalog

Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…

google/skills · 138 tokens