Malware Analysis logo

Malware Analysis

Community
hypnguyen1209
malware-analysis

Use when reverse-engineering or detecting malware — static triage + capa/YARA-X, emulation/DBI/.NET unpacking, dynamic/fileless/Volatility 3 memory analysis, C2 config extraction (Cobalt Strike/CAPE), C2 traffic detection (JA4+, beaconing)

Overview

Publisherhypnguyen1209
Repositoryoffensive-claude
Skill namemalware-analysis
Stars
396
Forks
71
Bundled files
13
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 13 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by hypnguyen1209 on GitHub. Read the source before you install it.

Installation

Install the Malware Analysis AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/malware-analysis
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude.git /tmp/offensive-claude
mkdir -p .claude/skills
cp -r /tmp/offensive-claude/skills/malware-analysis .claude/skills/malware-analysis
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Malware Analysis in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Malware Analysis on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Malware Analysis is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Malware Analysis

When to Activate

  • Triaging an unknown binary/script: identity, packing verdict, capability map, IOCs, go/no-go for detonation.
  • Recovering the real payload from a packed/crypted/obfuscated loader (commodity loaders, RAT chains, .NET).
  • Detonating safely and recovering fileless / in-memory artifacts (injection, AMSI/ETW patching, WMI persistence).
  • Extracting malware configuration (C2, keys, sleep/jitter, campaign IDs) for threat intel and detection.
  • Detecting/characterizing C2 on the wire (beacon cadence, JA4+ fingerprints, tunneled/DoH channels).
  • Writing durable, low-FP YARA-X detection from analysis findings; incident-response scoping.

Technique Map

TechniqueATT&CKCWEReferenceScript
Hash/imphash/Rich/ssdeep/TLSH triage + PE anomaliesT1027CWE-506references/static-triage-capa.mdscripts/triage.py
Per-section entropy + packer/RWX/EP heuristicsT1027.002CWE-1066references/static-triage-capa.mdscripts/triage.py
Obfuscated string recovery (FLOSS)T1140, T1027.013CWE-656references/static-triage-capa.mdscripts/triage.py
Capability detection → ATT&CK (capa, static+dynamic)T1027CWE-506references/static-triage-capa.mdscripts/triage.py
Emulation unpacking (Unicorn/unipacker/Speakeasy/Qiling)T1140, T1620CWE-656references/unpacking-deobfuscation.mdscripts/auto_unpack.py
DBI unpacking via API hooks (Frida)T1055, T1620CWE-656references/unpacking-deobfuscation.mdscripts/frida_unpack.js
.NET deobfuscation/unpacking (de4dot/dnSpyEx)T1027, T1140CWE-656references/unpacking-deobfuscation.mdscripts/frida_unpack.js
Sandbox detonation + behavioral captureT1497CWE-506references/dynamic-fileless-memory.mdscripts/mem_triage.py
Memory injection/hollowing/ghosting analysis (Vol3)T1055, T1055.012CWE-506references/dynamic-fileless-memory.mdscripts/mem_triage.py
AMSI/ETW in-memory patch + patchless detectionT1562.001CWE-693references/dynamic-fileless-memory.mdscripts/mem_triage.py
Fileless WMI/registry/PowerShell persistenceT1546.003, T1547.001, T1059.001CWE-506references/dynamic-fileless-memory.mdscripts/mem_triage.py
Cobalt Strike / AdaptixC2 config extractionT1071.001, T1573CWE-798references/config-c2-extraction.mdscripts/cs_config_extract.py
Config framework at scale (MACO/CAPE)T1071.001CWE-798references/config-c2-extraction.mdscripts/cs_config_extract.py
Generic unknown-C2 protocol RE + decoderT1573, T1071.004CWE-311references/config-c2-extraction.mdscripts/cs_config_extract.py
Beacon cadence/jitter detection (PCAP/Zeek)T1071.001, T1029CWE-778references/network-c2-detection.mdscripts/beacon_profiler.py
JA4+ TLS/HTTP/cert fingerprinting (Sliver/Havoc JA4X)T1071.001, T1573CWE-295references/network-c2-detection.mdscripts/beacon_profiler.py
Tunneled/DoH C2 surfacing (cloudflared/chisel)T1572, T1568.002, T1071.004CWE-441references/network-c2-detection.mdscripts/beacon_profiler.py
YARA-X family rule authoring + FP validationT1027CWE-506references/yara-detection-engineering.mdscripts/yara_gen.py

Quick Start

bash
# 1. Static triage: hashes + PE anomalies + capability combos + FLOSS/capa/YARA-X
python3 scripts/triage.py sample.exe --floss --capa --yara rules/family.yar --json out/triage.json
capa -j sample.exe > out/capa.json                       # capabilities -> ATT&CK

# 2. Unpack (try emulation first; DBI fallback in isolated VM)
python3 scripts/auto_unpack.py sample.exe -o out/dumps/  # static emulation, no detonation
frida -f C:\sample.exe -l scripts/frida_unpack.js --no-pause   # DBI, isolated VM only
de4dot sample.exe -o cleaned.exe                         # .NET layer

# 3. Dynamic + memory (capture mem BEFORE remediation)
python3 scripts/mem_triage.py -f mem.raw --vol vol --patch-hunt --json out/mem.json

# 4. Config + C2 extraction
python3 scripts/cs_config_extract.py beacon.bin --json    # Cobalt Strike
python3 1768.py -S beacon.bin                             # full CS incl. runtime/heap config
configextractor sample.bin                               # MACO/MWCP/CAPE at scale

# 5. Network C2 detection
python3 scripts/beacon_profiler.py capture.pcap --min-beacons 6     # cadence/jitter
zeek -r capture.pcap LOCAL ja4 && zeek-cut ja4 ja4s ja4x < ja4.log  # JA4+ pivots

# 6. Detection engineering
python3 scripts/yara_gen.py --family samples/fam/ --name Fam --goodware /usr/bin --out rules/fam.yar
yara-x fmt rules/fam.yar && yara-x scan rules/fam.yar /corpus/

OPSEC & Detection (summary)

TechniqueTelemetry/IOCDetection (Sigma/EDR)OPSEC note
Static triageNone (offline)n/a — feeds YARA/imphash huntingRead-only, no execution; isolate sample dir
Emulation unpackNone (no detonation)n/aPreferred first pass; safe, no network
DBI/manual unpackSysmon 8/10 (CallTrace UNKNOWN), RWX commitEDR memory scan; RWX-then-exec SigmaDETONATES — isolated VM, snapshot, FakeNet; loaders self-delete, dump first
Injection/hollowingmalfind/hollowprocesses; EID 8/10Vol3 hollow/ghosting/pebmasquerade; CreateRemoteThreadCapture memory pre-remediation
AMSI/ETW patchamsi.dll load + patched prologue; B8 00..C3 stubSigma T1562.001; debug-reg+VEH for patchlessPatchless evades byte scans — watch Dr0-Dr7
Fileless persistenceWMI consumers; PS 4104; Run-key blobsVol3 registry/wmi; Sysmon 13/22Lives in WMI/registry/memory — no disk file
Config extractionC2 host/UA/pipe/watermarkYARA config table; Suricata on C2 URI/SNIOffline; handle watermark/keys per ROE
Beacon detectionPeriodic outbound deltasbeacon_profiler CV score; Suricata thresholdPassive on captured traffic
JA4+ fingerprintJA4/JA4S/JA4X/JA4H tuplesZeek ja4 watchlist (Sliver/Havoc JA4X)JA4X needs TLS1.3 cert visibility at proxy
YARA-X authoringNoneThe rules themselvesValidate 0-FP on goodware before deploy

Deep Dives

  • references/static-triage-capa.md — Identity/code hashes, Rich header, entropy/packer heuristics, FLOSS, capa (PE/ELF/.NET/shellcode + dynamic capa over CAPE, Android rules, capa Explorer Web), FLARE-VM 2025.
  • references/unpacking-deobfuscation.md — Self-modifying-stub oracle, emulation (auto_unpack/unipacker/Speakeasy/Qiling), Frida DBI hooks, x64dbg→OEP→Scylla, .NET (de4dot/dnSpyEx), Latrodectus 1.4 AES strings, AsyncRAT fileless loaders, garble/pyc.
  • references/dynamic-fileless-memory.md — Sandbox build, Volatility 3 injection playbook + 2025 contest plugins (PEScan/Fileless Hunter), AMSI/ETW patch IOCs + patchless VEH bypass, WMI/registry/PS fileless persistence.
  • references/config-c2-extraction.md — Cobalt Strike (1768.py runtime config, CobaltStrikeParser XOR 0x69/0x2e), AdaptixC2 (Unit 42, 2025), MACO/configextractor-py/CAPEv2 at scale, generic unknown-C2 decoder methodology.
  • references/network-c2-detection.md — Beacon cadence/CV scoring, JA4+ suite (JA4X for randomized-cert Sliver/Havoc, Zeek/TheHive 2025-26), tunneled/DoH C2 (cloudflared/TryCloudflare/chisel), Suricata/Sigma + ransomware 2025 tradecraft.
  • references/yara-detection-engineering.md — YARA-X 1.0 (Rust, 99% compat, fmt/WASM, perf caveats), code/byte > string rules, pe/math modules, threshold logic, goodware FP validation, memory+disk scanning, capa pairing.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Malware Analysis AI skill do?

Use when reverse-engineering or detecting malware — static triage + capa/YARA-X, emulation/DBI/.NET unpacking, dynamic/fileless/Volatility 3 memory analysis, C2 config extraction (Cobalt Strike/CAPE), C2 traffic detection (JA4+, beaconing)

Why use Malware Analysis on TypingMind?

Because you install it once and use it with any model. Malware Analysis is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Malware Analysis in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/malware-analysis. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Malware Analysis?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Malware Analysis?

As many as you like. As long as a model supports skills, you can use Malware Analysis with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Malware Analysis AI skill free?

Yes. It is published on GitHub by hypnguyen1209 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇