dynamic-malware-analysis

dynamic-malware-analysis is a skill for Claude Code, Codex from ShulkwiSEC/bb-huge. It costs 41 tokens per session (1,013 once invoked), scanned A, original, MIT.

A guided method for running suspicious software in an isolated, monitored environment and recording what it does. It observes network traffic, file changes, registry changes, and hidden payloads revealed during execution.

In plain words
What is it for?
Investigating malware behavior, identifying contacted domains, finding dropped files and persistence methods, and extracting runtime configuration or later-stage payloads.
Why use it?
Static analysis can miss malware that is packed, encrypted, or obfuscated. Controlled execution shows its real behavior while reducing the risk to the analyst's system.

Skill for Claude CodeCodex

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

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is - [`_shared/references/elite-chaining-strategy.md`](../_shared/references/elite-chaining-strategy.md) — Exploit chaining methodology and high-payout chain patte.

Good fit Investigating malware behavior, identifying contacted domains, finding dropped files and persistence methods, and extracting runtime configuration or later-stage payloads.

Compare 6 skills from other repositories ↓
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/ShulkwiSEC/bb-huge
agentmods
npx agentmods add skills/shulkwisec/bb-huge/dynamic-malware-analysis

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 dynamic-malware-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/shulkwisec/bb-huge/dynamic-malware-analysis.svg)](https://agentmods.dev/skills/shulkwisec/bb-huge/dynamic-malware-analysis)
Your own site
<a href="https://agentmods.dev/skills/shulkwisec/bb-huge/dynamic-malware-analysis"><img src="https://agentmods.dev/badge/skills/shulkwisec/bb-huge/dynamic-malware-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,013 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.00041 $0.01013
Opus 5 $0.00020 $0.00507
Sonnet 5 $0.00008 $0.00203
Haiku 4.5 $0.00004 $0.00101

Measured 4d ago against content hash 152a610cd240, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

dynamic-malware-analysis 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 4d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/process.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/curated/dynamic-malware-analysis/SKILL.md · 116 lines

How it starts

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

Dynamic Malware Analysis

When to Use

  • When static analysis (examining the code without running it) is insufficient because the malware is heavily packed, encrypted, or obfuscated.
  • To rapidly understand the "blast radius" of a malicious payload (What files does it drop? What domains does it contact? What persistence mechanisms does it establish?).
  • When you need to extract decryption keys, Command & Control (C2) configurations, or secondary stage payloads that are only unlocked during runtime.

Prerequisites

  • Isolated analysis environment (VM with snapshot capability)
  • Sample file safely obtained and handled with appropriate precautions
  • PE analysis tools (PE-bear, CFF Explorer, Detect It Easy) installed
  • Disassembler/decompiler (Ghidra, IDA Free, or Binary Ninja) configured

Workflow

Phase 1: The Sandbox Environment (CRITICAL)

# Concept: NEVER run malware Setup 1. 2. 3. 4. ```

### Phase 2: Instrumentation (Setting the Traps)

```text
# Before detonation 1. Process Monitor (Procmon) 2. Wireshark 3. FakeNet / INetSim # ```

### Phase 3: Detonation and Observation

```bash
# # ```

### Phase 4: Analysis (Connecting the Dots)

```text
# 1. Behavioral 2. Network ```

#### Decision Point 🔀
```mermaid
flowchart TD
    A[Prepare Sandbox reliably ] --> B[Enable ]
    B --> C{Does ]}
    C -->|Yes| D[Log ]
    C -->|No| E[Check ]
    D --> F[Analyze ]

🔵 Blue Team Detection & Defense

  • Indicator of Compromise (IoC) Generation: The Behavioral Analytics: EDR Sandbox Evasion Detection: Malware Key Concepts | Concept | Description | |---------|-------------|

Output Format

Dynamic Malware Analysis — Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]

Findings Summary:
  [Finding 1]: [Severity] — [Brief description]
  [Finding 2]: [Severity] — [Brief description]

Detailed Results:
  Phase 1: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

  Phase 2: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
  1. [Immediate remediation step]
  2. [Long-term hardening measure]
  3. [Monitoring/detection improvement]

Read the full file on GitHub · 116 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago First seen · 116 lines · 41 tokens per session scan A 152a610cd240

Subscribe to this mod's changes

dynamic-malware-analysis is a skill published in the GitHub repository ShulkwiSEC/bb-huge (22 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,013 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

dynamic-malware-analysis

Execute and analyze malware samples within a highly controlled, instrumented sandbox environment to observe their true behavior, network communications, file system modifications, and registry changes in real-time.

akashrpatil/awesome-offensive-security-skills · 41 tokens

performing-dynamic-analysis-in-a-sandbox

Runs a sample in an instrumented sandbox to observe behavior: process tree, file and registry changes, network activity, and persistence, then summarizes the behavioral report into capabilities and IOCs. Activates for requests to detonate a sample, do dynamic or behavioral analysis, or interpret sandbox output.

meltedinhex/analyst-ai-pack · 68 tokens

analyzing-malware-behavior-with-cuckoo-sandbox

Detonate malware samples in Cuckoo Sandbox to observe runtime behavior — process creation, file system and registry changes, network communications, and API calls — and generate behavioral reports for classification and IOC extraction. Use when a sample has passed static triage and needs dynamic/behavioral analysis…

mukul975/Anthropic-Cybersecurity-Skills · 93 tokens

analyzing-api-call-traces

Analyzes API call traces from a sandbox or API monitor (JSON) to group calls by category, reconstruct high-level behaviors (process injection, file drops, network, crypto), and flag suspicious call sequences. Activates for requests to analyze an API trace, interpret sandbox API logs, or identify behavior from…

meltedinhex/analyst-ai-pack · 75 tokens

monitoring-process-and-file-behavior

Summarizes runtime behavior of a sample from Procmon-style operation logs — process and thread creation, file and registry writes, and network-related operations — to build a behavioral profile. Activates for requests to analyze Procmon output, summarize sample behavior, or profile process/file/registry activity from…

meltedinhex/analyst-ai-pack · 71 tokens

analyzing-golang-malware-with-ghidra

Reverse engineer Go-compiled malware in Ghidra by parsing Go buildinfo and pclntab structures, recovering stripped/obfuscated function names (e.g. via GoResolver), and extracting embedded module/dependency strings and types from Go binaries. Use when analyzing a Go-language malware sample, deobfuscating a…

mukul975/Anthropic-Cybersecurity-Skills · 95 tokens