analyzing-packed-malware-with-upx-unpacker

analyzing-packed-malware-with-upx-unpacker is a skill for Claude Code from mukul975/Anthropic-Cybersecurity-Skills. It costs 88 tokens per session (3,159 once invoked), scanned A, original, Apache-2.0.

A malware-analysis guide for unpacking Windows executables compressed or hidden with UPX, a tool that reduces executable size and can obscure its contents. It also covers samples with changed UPX headers that prevent normal extraction.

In plain words
What is it for?
Use it when a sample has high-entropy sections, few imports, or is identified as UPX-packed. It helps restore damaged headers and extract the original program for further analysis.
Why use it?
Packed files can hide the code and imports needed for static analysis. Recovering the original executable makes it easier to inspect in tools such as Ghidra or IDA.

Skill for Claude Code

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

Part of the cybersecurity-skills plugin — 56 skills shipped together

Good fit Use it when a sample has high-entropy sections, few imports, or is identified as UPX-packed. It helps restore damaged headers and extract the original program for further analysis.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mukul975/anthropic-cybersecurity-skills/analyzing-packed-malware-with-upx-unpacker
About the project

Anthropic Cybersecurity Skills is a library of structured cybersecurity procedures for AI agents, covering security domains and mappings to established security frameworks. It is for authorized security analysis, penetration testing, incident response, research, defense, and education across compatible AI platforms. The catalogue entries package parts of this library as agent skills, instructions, or a plugin.

mukul975/Anthropic-Cybersecurity-Skills · 32,631 stars · on GitHub · mahipal.engineer

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 mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-packed-malware-with-upx-unpacker
Clone the repo
git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills

Made for: Claude Code.

Or install cybersecurity-skills, the plugin that ships this one along with the rest of its 56 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-packed-malware-with-upx-unpacker

README.md
[![agentmods](https://agentmods.dev/badge/skills/mukul975/anthropic-cybersecurity-skills/analyzing-packed-malware-with-upx-unpacker/github.svg)](https://agentmods.dev/skills/mukul975/anthropic-cybersecurity-skills/analyzing-packed-malware-with-upx-unpacker)
Your own site
<a href="https://agentmods.dev/skills/mukul975/anthropic-cybersecurity-skills/analyzing-packed-malware-with-upx-unpacker"><img src="https://agentmods.dev/badge/skills/mukul975/anthropic-cybersecurity-skills/analyzing-packed-malware-with-upx-unpacker/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 analyzing-packed-malware-with-upx-unpacker

Your own site · 80×15
<a href="https://agentmods.dev/skills/mukul975/anthropic-cybersecurity-skills/analyzing-packed-malware-with-upx-unpacker"><img src="https://agentmods.dev/badge/skills/mukul975/anthropic-cybersecurity-skills/analyzing-packed-malware-with-upx-unpacker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,159 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. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00088 $0.03159
Opus 5 $0.00044 $0.01580
Sonnet 5 $0.00018 $0.00632
Haiku 4.5 $0.00009 $0.00316

Measured 13d ago against content hash 06379c741ea5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

analyzing-packed-malware-with-upx-unpacker 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 13d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/agent.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

6 near-identical copies found in the catalogue:

skills/analyzing-packed-malware-with-upx-unpacker/SKILL.md · 312 lines

How it starts

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

Analyzing Packed Malware with UPX Unpacker

When to Use

  • Static analysis reveals high entropy sections and minimal imports indicating the binary is packed
  • PEiD, Detect It Easy, or PEStudio identifies UPX or another known packer
  • The import table contains only LoadLibrary and GetProcAddress (runtime import resolution typical of packed binaries)
  • You need to recover the original binary for proper disassembly and decompilation in Ghidra or IDA
  • Automated UPX decompression fails because the malware author modified UPX magic bytes or headers

Do not use when dealing with custom packers, VM-based protectors (Themida, VMProtect), or samples where dynamic unpacking via debugging is more appropriate.

Prerequisites

  • UPX (Ultimate Packer for eXecutables) installed (apt install upx-ucl or download from https://upx.github.io/)
  • Detect It Easy (DIE) for packer identification
  • Python 3.8+ with pefile library for manual header repair
  • x64dbg or x32dbg for manual unpacking when automated tools fail
  • PE-bear or CFF Explorer for PE header inspection and repair
  • Isolated analysis VM without network connectivity

Workflow

Step 1: Identify the Packer

Determine if the sample is packed and identify the packer:

# Check with Detect It Easy
diec suspect.exe

# Check with UPX (test without unpacking)
upx -t suspect.exe

# Python-based entropy and packer detection
python3 << 'PYEOF'
import pefile
import math

pe = pefile.PE("suspect.exe")

print("Section Analysis:")
for section in pe.sections:
    name = section.Name.decode().rstrip('\x00')
    entropy = section.get_entropy()
    raw = section.SizeOfRawData
    virtual = section.Misc_VirtualSize
    print(f"  {name:8s} Entropy: {entropy:.2f}  Raw: {raw:>8}  Virtual: {virtual:>8}")

# Check for UPX section names
section_names = [s.Name.decode().rstrip('\x00') for s in pe.sections]
if 'UPX0' in section_names or 'UPX1' in section_names:
    print("\n[!] UPX section names detected")
elif '.upx' in [s.lower() for s in section_names]:
    print("\n[!] UPX variant section names detected")

# Check import count (packed binaries have very few)
if hasattr(pe, 'DIRECTORY_ENTRY_IMPORT'):
    total_imports = sum(len(e.imports) for e in pe.DIRECTORY_ENTRY_IMPORT)
    print(f"\nTotal imports: {total_imports}")
    if total_imports < 10:
        print("[!] Very few imports - likely packed")
else:
    print("\n[!] No import directory - heavily packed")
PYEOF

Read the full file on GitHub · 312 lines

Files

What ships with it

3 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. 13d ago First seen · 312 lines · 88 tokens per session scan A 06379c741ea5

Subscribe to this mod's changes

analyzing-packed-malware-with-upx-unpacker is a skill published in the GitHub repository mukul975/Anthropic-Cybersecurity-Skills (32,631 stars, last pushed 12d ago), licensed Apache-2.0. It adds 88 tokens to every session and 3,159 once invoked, about $0.0004 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 skills, from other repositories

analyzing-packed-malware-with-upx-unpacker

Identifies and unpacks UPX-packed and other packed malware samples to expose the original executable code for static analysis. Covers both standard UPX unpacking and handling modified UPX headers that prevent automated decompression. Activates for requests involving malware unpacking, UPX decompression, packer…

26zl/cybersec-toolkit · 79 tokens

analyzing-packed-malware-with-upx-unpacker

Identifies and unpacks UPX-packed and other packed malware samples to expose the original executable code for static analysis. Covers both standard UPX unpacking and handling modified UPX headers that prevent automated decompression. Activates for requests involving malware unpacking, UPX decompression, packer…

Mikaru0Mystic/sectinel · 79 tokens

analyzing-packed-malware-with-upx-unpacker

A guide for unpacking Windows executable files protected by UPX or a similar packing tool. Packing compresses or hides the original program code, making ordinary inspection harder.

killvxk/cybersecurity-skills-zh · 104 tokens

analyzing-packed-malware-with-upx-unpacker

Identifies and unpacks UPX-packed and other packed malware samples to expose the original executable code for static analysis. Covers both standard UPX unpacking and handling modified UPX headers that prevent automated decompression. Activates for requests involving malware unpacking, UPX decompression, packer…

pinkpixel-dev/skills-collection-1 · 79 tokens

analyzing-packed-malware-with-upx-unpacker

Identifies and unpacks UPX-packed and other packed malware samples to expose the original executable code for static analysis. Covers both standard UPX unpacking and handling modified UPX headers that prevent automated decompression. Activates for requests involving malware unpacking, UPX decompression, packer…

marysatasselshaped667/skills-collection-1 · 79 tokens

analyzing-packed-malware-with-upx-unpacker

Identifies and unpacks UPX-packed and other packed malware samples to expose the original executable code for static analysis. Covers both standard UPX unpacking and handling modified UPX headers that prevent automated decompression. Activates for requests involving malware unpacking, UPX decompression, packer…

autohandai/community-skills · 79 tokens