malware-analyst

malware-analyst is an agent for Claude Code from 0xSteph/pentest-ai-agents. It costs 44 tokens per session (4,836 once invoked), scanned A, original, MIT.

A security-analysis specialist for examining suspicious files and software to understand what they do. It covers malware analysis, reverse engineering, disassembly, debugging, and both static and dynamic analysis.

In plain words
What is it for?
Use it to identify and triage suspicious files, inspect binaries and scripts, analyze behavior in isolated environments, and relate findings to MITRE ATT&CK, a catalog of common attacker techniques.
Why use it?
It helps organize the investigation of potentially malicious files without running them unsafely or overlooking important evidence. It also records indicators of compromise, such as hashes and other signs that systems may be affected.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the pentest-ai-agents plugin — 3 commands, 52 agents shipped together

About the project

0xSteph/pentest-ai-agents is a collection of Claude Code specialist agents for authorized penetration testing and security research, covering areas such as reconnaissance, web systems, cloud, reverse engineering and detection. Security researchers and penetration testers use it to plan engagements, investigate findings, build detections and write reports. The catalogue entries are the project's own agents, commands and plugin components.

0xSteph/pentest-ai-agents · 2,198 stars · on GitHub · pentestai.xyz

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/0xsteph/pentest-ai-agents/malware-analyst
Clone the repo
git clone --depth 1 https://github.com/0xSteph/pentest-ai-agents

Made for: Claude Code.

Or install pentest-ai-agents, the plugin that ships this one along with the rest of its 3 commands, 52 agents.

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 malware-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/0xsteph/pentest-ai-agents/malware-analyst.svg)](https://agentmods.dev/agents/0xsteph/pentest-ai-agents/malware-analyst)
Your own site
<a href="https://agentmods.dev/agents/0xsteph/pentest-ai-agents/malware-analyst"><img src="https://agentmods.dev/badge/agents/0xsteph/pentest-ai-agents/malware-analyst.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,836 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00044 $0.04836
Opus 5 $0.00022 $0.02418
Sonnet 5 $0.00009 $0.00967
Haiku 4.5 $0.00004 $0.00484

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

Security

Grade A, and why

malware-analyst scanned grade A with 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/malware-analyst.md · 311 lines

How it starts

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

You are an expert malware analyst and reverse engineer specializing in dissecting malicious software, extracting indicators of compromise, and producing actionable intelligence from suspicious binaries and scripts. All work is performed within the scope of authorized security engagements and incident response.

Core Principles

  1. Always start with static analysis before executing anything dynamically.
  2. Work exclusively in isolated analysis environments. Never run suspicious samples on production or connected systems.
  3. Extract and document all indicators of compromise systematically throughout the analysis.
  4. Map every observed behavior to MITRE ATT&CK techniques.
  5. Consider the malware author's intent and sophistication level when interpreting findings.
  6. Note confidence levels (high, medium, low) for each finding based on the strength of available evidence.

Static Analysis

File Identification and Triage

Begin every analysis by establishing what you are working with:

  • File type identification: Use file, TrID, and magic byte inspection to determine the true file type regardless of extension
  • Cryptographic hashes: Generate MD5, SHA-1, and SHA-256 hashes for every sample
  • Hash lookups: Query VirusTotal, MalwareBazaar, Hybrid Analysis, and other threat intelligence platforms to check for prior submissions and existing analysis
  • Fuzzy hashing: Use ssdeep or TLSH to identify similar samples in your corpus
  • File size and timestamps: Record all metadata including compile timestamps, which may indicate origin or be deliberately falsified

Strings Extraction

  • Run strings (both ASCII and Unicode) and review output for URLs, IP addresses, file paths, registry keys, mutexes, commands, error messages, and embedded credentials
  • Use FLOSS (FireEye Labs Obfuscated String Solver) to extract obfuscated and stack strings that standard strings will miss
  • Look for base64-encoded blobs, XOR patterns, and encoded configuration data
  • Identify debug strings, PDB paths, and build artifacts that reveal development environment details

Read the full file on GitHub · 311 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 · 311 lines · 44 tokens per session scan A c19a2f915d09

Subscribe to this mod's changes

malware-analyst is an agent published in the GitHub repository 0xSteph/pentest-ai-agents (2,198 stars, last pushed 20d ago), licensed MIT. It adds 44 tokens to every session and 4,836 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

tachi-denial-of-service

STRIDE denial of service threat agent that detects availability degradation threats against Processes, Data Stores, and Data Flows, covering resource exhaustion, algorithmic complexity attacks, connection pool exhaustion, and cascading dependency failures.

davidmatousek/tachi · 48 tokens

Incident Response Commander

Expert incident commander specializing in production incident management, structured response coordination, post-mortem facilitation, SLO/SLI tracking, and on-call process design for reliable engineering organizations.

SHAdd0WTAka/Zen-Ai-Pentest · 41 tokens

Minimal Change Engineer

Engineering specialist focused on minimum-viable diffs — fixes only what was asked, refuses scope creep, prefers three similar lines over a premature abstraction. The discipline that prevents bug-fix PRs from becoming refactor avalanches.

SHAdd0WTAka/Zen-Ai-Pentest · 50 tokens

exploit

Exploitation specialist for gaining initial access. Use when exploiting CVEs, running Metasploit modules, using searchsploit, obtaining shells, or executing proof-of-concept code. Triggers on: exploit, CVE-, initial access, get shell, msfconsole, owned, pwn, vulnerability exploit, remote code execution, RCE.

mukul975/Threatswarm · 73 tokens

iot-attacker

IoT and embedded systems security specialist. Handles firmware extraction and analysis, hardcoded credential discovery, UART/JTAG access, MQTT/CoAP protocol testing, RouterSploit exploitation, web interface attacks, and OT/ICS protocol analysis. Triggers on: IoT, firmware, binwalk, UART, JTAG, router, embedded…

mukul975/Threatswarm · 93 tokens

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens