malware-analysis-reversing

malware-analysis-reversing is a skill for Claude Code, Codex from hamzabellouch/agent-skills. It costs 39 tokens per session (1,886 once invoked), scanned A, original, MIT.

A defensive guide to examining suspicious software, including isolated testing, file inspection, runtime monitoring, memory analysis, and YARA rules for detecting threats.

In plain words
What is it for?
Use it for malware triage, reverse engineering, incident response, memory forensics, and writing YARA detection rules.
Why use it?
It provides a structured way to understand potentially harmful programs while reducing the risk of running them on live systems.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for malware triage, reverse engineering, incident response, memory forensics, and writing YARA detection rules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hamzabellouch/agent-skills/malware-analysis-reversing
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.

Any agent
npx skills add hamzabellouch/agent-skills --skill malware-analysis-reversing
Clone the repo
git clone --depth 1 https://github.com/hamzabellouch/agent-skills

Made for: Claude Code, Codex.

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-analysis-reversing

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/malware-analysis-reversing/github.svg)](https://agentmods.dev/skills/hamzabellouch/agent-skills/malware-analysis-reversing)
Your own site
<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/malware-analysis-reversing"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/malware-analysis-reversing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for malware-analysis-reversing

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/malware-analysis-reversing"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/malware-analysis-reversing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,886 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00039 $0.01886
Opus 5 $0.00019 $0.00943
Sonnet 5 $0.00008 $0.00377
Haiku 4.5 $0.00004 $0.00189

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

Security

Grade A, and why

malware-analysis-reversing 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 8d 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.

Cybersecurity and Penetration Testing/malware-analysis-reversing/SKILL.md · 176 lines

How it starts

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

Malware Analysis & Reverse Engineering Architecture

Overview

This skill provides technical standards and defensive methodologies for malware analysis and reverse engineering. It covers isolated sandbox setup, static binary inspection (PE/ELF headers, imported functions, packed section detection), dynamic behavior monitoring, memory dump forensics, and authoring YARA rules for threat detection and incident response.


1. Malware Analysis Principles & Safety Protocols

  1. Strict Air-Gapped / Isolated Sandbox: Always perform malware execution and dynamic monitoring inside isolated virtual machines (REMnux, FLARE VM) with network isolation (INetSim / FakeNet-NG) to prevent lateral movement or C2 callbacks to live networks.
  2. Layered Analysis Methodology:
    • Static Triage: File hashing (MD5, SHA256, ssdeep), PE/ELF header analysis, string extraction, and packer detection (PEiD / Detect It Easy).
    • Dynamic Triage: API monitoring, registry/filesystem access tracking (ProcMon), network packet capturing (Wireshark).
    • Code-Level Disassembly / Decompilation: Reverse engineering control flow and functions using Ghidra or IDA Pro.
    • Memory Forensics: Extracting decrypted payloads or process injection artifacts from volatile memory dumps via Volatility 3.
  3. Automated Indicator Extraction (IOCs): Extract high-confidence Indicators of Compromise (IP addresses, domain names, file hashes, registry run keys, mutexes) for SIEM ingest.
  4. Defensive YARA Rule Generation: Write precise YARA detection rules targeting unique string signatures and byte patterns while minimizing false positives.

2. Reverse Engineering & Analysis Pipeline

[ Suspicious Binary Sample ]
       │
       ├──▶ [ 1. Static Analysis ] ──(Hashes, PE Headers, Import Table, Strings)
       │
       ├──▶ [ 2. Dynamic Sandbox ] ──(Process Trees, File/Registry Mutations, PCAP)
       │
       ├──▶ [ 3. Code Reversing ] ───(Ghidra Decompiler, Disassembly Control Flow)
       │
       └──▶ [ 4. Memory Forensics ] ─(Volatility 3 Dump, Extracted Payloads)
               │
               ▼
[ Threat Intelligence & YARA Detection Rules ]

Read the full file on GitHub · 176 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. 8d ago First seen · 176 lines · 39 tokens per session scan A 6cbdca86b0f3

Subscribe to this mod's changes

malware-analysis-reversing is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,886 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-09-03.

Related

Other skills, from other repositories

spec-create

Create a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture…

benjaminthomas/spec-driven-dev · 118 tokens

spec-implement

Orchestrate parallel implementation of a feature specification by dispatching coder agents batch-by-batch with code review gates between batches. Use this skill when the user says "implement this feature", "start implementing", "run the spec", "execute the plan", "continue implementing", or wants to begin coding a…

benjaminthomas/spec-driven-dev · 130 tokens

spec-ship

Push the current branch to GitHub and create a pull request. Use this skill when the user says "ship it", "ship this", "push to github", "create a pr", "open a pull request", "send for review", "get this reviewed", or wants to push their work and open a PR. Also use when the user says "/spec-ship" (or their host's…

benjaminthomas/spec-driven-dev · 119 tokens

spec-checkpoint

Create a comprehensive checkpoint commit with detailed analysis of all changes. Use this skill when the user says "checkpoint", "commit everything", "save my progress", "create a commit", or wants to stage and commit all current changes with a well-crafted message. Also use when the user says "/spec-checkpoint" (or…

benjaminthomas/spec-driven-dev · 98 tokens

generative-seo

Run an evidence-based SEO + GEO (Generative Engine Optimization) program for ANY website or product codebase — auditing technical SEO, writing or retrofitting content so it gets cited by ChatGPT/Perplexity/AI Overviews, tracking AI-citation visibility, refreshing competitor research, and drafting distribution posts.…

benjaminthomas/spec-driven-dev · 180 tokens

spec-verify

Verify a completed feature spec by driving the real running app — not just lint/typecheck/build — and checking off every acceptance criterion from its specs/{feature}/ folder one by one. Use this after /spec-implement finishes a spec, when the user says "test this end to end", "verify this feature actually works"…

benjaminthomas/spec-driven-dev · 210 tokens