Agent skill

Performing Static Malware Analysis With Pe Studio

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Performs static analysis of Windows PE malware samples using PEStudio to examine file headers, imports, strings, and resources without executing the binary, identifying packing, anti-analysis…

Apache-2.0Auto-check passedSecurity

Install Performing Static Malware Analysis With Pe Studio

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-static-malware-analysis-with-pe-studio -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills performing-static-malware-analysis-with-pe-studio --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/performing-static-malware-analysis-with-pe-studio .claude/skills/performing-static-malware-analysis-with-pe-studio && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
performing-static-malware-analysis-with-pe-studio
GitHub stars
34k
Token cost
~3.3k tokens
SKILL.md length
699 words
Files
4 (incl. scripts, references)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Performs static analysis of Windows PE malware samples using PEStudio to examine file headers, imports, strings, and resources without executing the binary, identifying packing, anti-analysis…

  • Works in 7 steps: Compute File Hashes and Verify Sample… → Examine PE Headers and Section Table → Analyze Import Address Table (IAT) → …
  • Pre-execution triage of a suspicious Windows executable before sandbox detonation
  • SKILL.md covers When to Use, Prerequisites, Workflow and Key Concepts, plus 3 more sections
  • Runs Python scripts from its folder; calls curl, jq and python3; reaches virustotal.com; needs VT_API_KEY

What it does

Performing Static Malware Analysis With Pe Studio is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Performs static analysis of Windows PE malware samples using PEStudio to examine file headers, imports, strings, and resources without executing the binary, identifying packing, anti-analysis tricks, and malicious imports. Use for pre-execution triage of a suspicious Windows executable before sandbox detonation.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).

It sits in Security, covering Reverse engineering and malware and Static analysis and SAST. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Pre-execution triage of a suspicious Windows executable before sandbox detonation
  • Tasks that involve Reverse engineering and malware
  • Tasks that involve Static analysis and SAST

Example prompts

  • “Use the performing-static-malware-analysis-with-pe-studio skill to perform static analysis of Windows PE malware samples using PEStudio to examine…”
  • “/performing-static-malware-analysis-with-pe-studio”

Requirements

  • Python 3
  • A credential in VT_API_KEY

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Compute File Hashes and Verify Sample Integrity
  2. Examine PE Headers and Section Table
  3. Analyze Import Address Table (IAT)
  4. Extract and Analyze Strings
  5. Inspect Resources and Embedded Data
  6. Check for Packing and Protection
  7. Generate Static Analysis Report

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • curl
    • jq
    • python3
    • packer
    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • virustotal.com

    Also links to:

    • winitor.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • VT_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Performing Static Malware Analysis With Pe Studio loads about 3.3k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 699 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 699 words, ~3,289 tokens.

Download SKILL.mdSave it as .claude/skills/performing-static-malware-analysis-with-pe-studio/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
performing-static-malware-analysis-with-pe-studio
description
Performs static analysis of Windows PE malware samples using PEStudio to examine file headers, imports, strings, and resources without executing the binary, identifying packing, anti-analysis tricks, and malicious imports. Use for pre-execution triage of a suspicious Windows executable before sandbox detonation.
domain
cybersecurity
subdomain
malware-analysis
tags
malware, static-analysis, PE-analysis, PEStudio, reverse-engineering
version
1.0.0
author
mahipal
license
Apache-2.0
nist_csf
DE.AE-02, RS.AN-03, ID.RA-01, DE.CM-01
mitre_attack
T1027, T1055, T1140, T1497, T0816

Performing Static Malware Analysis with PEStudio

When to Use

  • A suspicious Windows executable has been collected and needs initial triage before sandbox execution
  • You need to identify imports, strings, and resources that reveal malware functionality without running the sample
  • Determining whether a PE file is packed, obfuscated, or contains anti-analysis techniques
  • Extracting indicators of compromise (hashes, URLs, IPs, registry keys) embedded in a binary
  • Classifying a sample's capabilities based on its import table and section characteristics

Do not use for dynamic behavioral analysis requiring execution; use a sandbox (Cuckoo, ANY.RUN) for runtime behavior observation.

Prerequisites

  • PEStudio (free edition from https://www.winitor.com/) installed on an isolated analysis workstation
  • Python 3.8+ with pefile library for scripted PE analysis (pip install pefile)
  • CFF Explorer or PE-bear as supplementary PE analysis tools
  • Access to VirusTotal API for hash lookups and community intelligence
  • Isolated analysis VM with no network connectivity to production systems
  • FLOSS (FireEye Labs Obfuscated String Solver) for extracting obfuscated strings

Workflow

Step 1: Compute File Hashes and Verify Sample Integrity

Generate cryptographic hashes for identification and intelligence lookup:

bash
# Generate MD5, SHA-1, and SHA-256 hashes
md5sum suspect.exe
sha1sum suspect.exe
sha256sum suspect.exe

# Check hash against VirusTotal
curl -s -X GET "https://www.virustotal.com/api/v3/files/$(sha256sum suspect.exe | cut -d' ' -f1)" \
  -H "x-apikey: $VT_API_KEY" | jq '.data.attributes.last_analysis_stats'

# Get file type with magic bytes verification
file suspect.exe
Step 2: Examine PE Headers and Section Table

Open the sample in PEStudio and inspect structural properties:

PEStudio Analysis Points:
━━━━━━━━━━━━━━━━━━━━━━━━━
File Header:       Compilation timestamp, target architecture (x86/x64)
Optional Header:   Entry point address, image base, subsystem (GUI/console)
Section Table:     Section names, virtual/raw sizes, entropy values
                   High entropy (>7.0) in .text/.rsrc suggests packing
Signatures:        Authenticode signature presence and validity

Scripted PE Header Analysis with pefile:

python
import pefile
import hashlib
import math

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

# Compilation timestamp
import datetime
timestamp = pe.FILE_HEADER.TimeDateStamp
compile_time = datetime.datetime.utcfromtimestamp(timestamp)
print(f"Compile Time: {compile_time} UTC")

# Section analysis with entropy calculation
for section in pe.sections:
    name = section.Name.decode().rstrip('\x00')
    entropy = section.get_entropy()
    raw_size = section.SizeOfRawData
    virtual_size = section.Misc_VirtualSize
    ratio = virtual_size / raw_size if raw_size > 0 else 0
    print(f"Section: {name:8s} Entropy: {entropy:.2f} Raw: {raw_size:>10} Virtual: {virtual_size:>10} Ratio: {ratio:.2f}")
    if entropy > 7.0:
        print(f"  [!] HIGH ENTROPY - likely packed or encrypted")
    if ratio > 10:
        print(f"  [!] HIGH V/R RATIO - unpacking stub likely present")
Step 3: Analyze Import Address Table (IAT)

Identify suspicious API imports that indicate malware capabilities:

python
# Extract and categorize imports
suspicious_imports = {
    "Process Injection": ["VirtualAllocEx", "WriteProcessMemory", "CreateRemoteThread", "NtCreateThreadEx"],
    "Keylogging": ["GetAsyncKeyState", "SetWindowsHookExA", "GetKeyState"],
    "Persistence": ["RegSetValueExA", "CreateServiceA", "SchTasksCreate"],
    "Evasion": ["IsDebuggerPresent", "CheckRemoteDebuggerPresent", "NtQueryInformationProcess"],
    "Network": ["InternetOpenA", "HttpSendRequestA", "URLDownloadToFileA", "WSAStartup"],
    "File Operations": ["CreateFileA", "WriteFile", "DeleteFileA", "MoveFileA"],
    "Crypto": ["CryptEncrypt", "CryptDecrypt", "CryptAcquireContextA"],
}

for entry in pe.DIRECTORY_ENTRY_IMPORT:
    dll_name = entry.dll.decode()
    for imp in entry.imports:
        if imp.name:
            func_name = imp.name.decode()
            for category, funcs in suspicious_imports.items():
                if func_name in funcs:
                    print(f"[!] {category}: {dll_name} -> {func_name}")
Step 4: Extract and Analyze Strings

Use FLOSS for obfuscated strings and standard strings extraction:

bash
# Standard strings extraction (ASCII and Unicode)
strings -a suspect.exe > strings_ascii.txt
strings -el suspect.exe > strings_unicode.txt

# FLOSS for decoded/deobfuscated strings
floss suspect.exe --output-json floss_output.json

# Search for network indicators in strings
grep -iE "(http|https|ftp)://" strings_ascii.txt
grep -iE "([0-9]{1,3}\.){3}[0-9]{1,3}" strings_ascii.txt
grep -iE "[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}" strings_ascii.txt

# Search for registry keys
grep -i "HKLM\\|HKCU\\|SOFTWARE\\|CurrentVersion\\Run" strings_ascii.txt

# Search for file paths and extensions
grep -iE "\.(exe|dll|bat|ps1|vbs|tmp)" strings_ascii.txt
Step 5: Inspect Resources and Embedded Data

Examine the PE resource section for embedded payloads or configuration:

python
# Extract resources from PE file
if hasattr(pe, 'DIRECTORY_ENTRY_RESOURCE'):
    for resource_type in pe.DIRECTORY_ENTRY_RESOURCE.entries:
        if hasattr(resource_type, 'directory'):
            for resource_id in resource_type.directory.entries:
                if hasattr(resource_id, 'directory'):
                    for resource_lang in resource_id.directory.entries:
                        data = pe.get_data(resource_lang.data.struct.OffsetToData,
                                          resource_lang.data.struct.Size)
                        entropy = calculate_entropy(data)
                        print(f"Resource Type: {resource_type.id} Size: {len(data)} Entropy: {entropy:.2f}")
                        if entropy > 7.0:
                            print(f"  [!] High entropy resource - possible embedded payload")
                        # Check for PE signature in resource (embedded executable)
                        if data[:2] == b'MZ':
                            print(f"  [!] Embedded PE detected in resource")
                            with open(f"extracted_resource_{resource_type.id}.bin", "wb") as f:
                                f.write(data)
Step 6: Check for Packing and Protection

Determine if the binary is packed or protected:

bash
# Detect packer with Detect It Easy (DIE)
diec suspect.exe

# Check with PEiD signatures (command-line version)
python3 -c "
import pefile
pe = pefile.PE('suspect.exe')
# Check for common packer section names
packer_sections = {'.upx0': 'UPX', '.aspack': 'ASPack', '.adata': 'ASPack',
                   '.nsp0': 'NsPack', '.vmprotect': 'VMProtect', '.themida': 'Themida'}
for section in pe.sections:
    name = section.Name.decode().rstrip('\x00').lower()
    if name in packer_sections:
        print(f'[!] Packer detected: {packer_sections[name]} (section: {name})')

# Check import table size (very few imports suggest packing)
import_count = sum(len(entry.imports) for entry in pe.DIRECTORY_ENTRY_IMPORT)
if import_count < 10:
    print(f'[!] Only {import_count} imports - likely packed')
"
Step 7: Generate Static Analysis Report

Compile all findings into a structured triage report:

Document the following for each analyzed sample:
- File identification (hashes, file type, size, compile timestamp)
- Packing/protection status and identified packer
- Suspicious imports categorized by capability
- Network indicators extracted from strings (IPs, domains, URLs)
- Embedded resources and their characteristics
- Overall threat assessment and recommended next steps (sandbox execution, YARA rule creation)

Key Concepts

TermDefinition
PE (Portable Executable)The file format for Windows executables (.exe, .dll, .sys) containing headers, sections, imports, and resources that define how the OS loads the binary
Import Address Table (IAT)PE structure listing external DLL functions the executable calls at runtime; reveals program capabilities and intent
Section EntropyStatistical measure of randomness in a PE section; values above 7.0 (out of 8.0) indicate compression, encryption, or packing
FLOSSFireEye Labs Obfuscated String Solver; automatically extracts and decodes obfuscated strings that standard strings misses
PackingCompression or encryption of a PE file's code section to hinder static analysis; requires runtime unpacking stub to execute
PE ResourcesData section within a PE file that can contain icons, dialogs, version info, or attacker-embedded payloads and configuration data
Compilation TimestampTimestamp in the PE header indicating when the binary was compiled; can be forged but often reveals development timeline
Show full SKILL.md (276 more words)Show less

Tools & Systems

  • PEStudio: Free Windows tool for static analysis of PE files providing indicators, imports, strings, and resource inspection in a single interface
  • pefile (Python): Python library for parsing and analyzing PE file structures programmatically for automated analysis pipelines
  • FLOSS: FireEye tool that extracts obfuscated strings from malware using static analysis techniques including stack string decoding
  • Detect It Easy (DIE): Packer and compiler detection tool that identifies protectors, compilers, and linkers used to build PE files
  • CFF Explorer: Advanced PE editor and viewer for detailed inspection of PE headers, sections, imports, and resource directories

Common Scenarios

Scenario: Triaging a Suspicious Email Attachment

Context: SOC receives an alert on a suspicious executable attached to a phishing email. The file needs rapid triage to determine if it is malicious before committing sandbox resources.

Approach:

  1. Compute SHA-256 hash and query VirusTotal for existing detections and community comments
  2. Open in PEStudio and check the indicators tab for red/yellow flagged items
  3. Verify compile timestamp (future dates or dates from 1970 indicate timestamp manipulation)
  4. Check imports for VirtualAllocEx, CreateRemoteThread (injection), URLDownloadToFileA (downloader)
  5. Extract strings and search for C2 URLs, IP addresses, and file paths
  6. Check resources for embedded PE files or high-entropy data blobs
  7. Assess packing status; if packed, note the packer and plan for unpacking before deeper analysis

Pitfalls:

  • Trusting the PE compile timestamp without corroborating evidence (timestamps are trivially forged)
  • Concluding a file is benign because it has few suspicious imports (packed malware hides real imports)
  • Missing Unicode strings by only running ASCII string extraction
  • Not checking overlay data appended after the last PE section (common hiding spot for configuration data)

Output Format

STATIC MALWARE ANALYSIS REPORT
=================================
Sample:           suspect.exe
MD5:              d41d8cd98f00b204e9800998ecf8427e
SHA-256:          e3b0c44298fc1c149afbf4c8996fb924...
File Size:        245,760 bytes
File Type:        PE32 executable (GUI) Intel 80386
Compile Time:     2025-09-14 08:23:15 UTC

PACKING STATUS
Packer Detected:  None (native binary)
Section Entropy:  .text=6.42 .rdata=4.89 .data=3.21 .rsrc=7.81
Note:             .rsrc section entropy elevated - check resources

SUSPICIOUS IMPORTS
[INJECTION]       kernel32.dll -> VirtualAllocEx
[INJECTION]       kernel32.dll -> WriteProcessMemory
[INJECTION]       kernel32.dll -> CreateRemoteThread
[EVASION]         kernel32.dll -> IsDebuggerPresent
[NETWORK]         wininet.dll  -> InternetOpenA
[NETWORK]         wininet.dll  -> HttpSendRequestA
[PERSISTENCE]     advapi32.dll -> RegSetValueExA

EXTRACTED INDICATORS
URLs:             hxxps://update.malicious[.]com/gate.php
IPs:              185.220.101[.]42, 91.215.85[.]17
Registry Keys:    HKCU\Software\Microsoft\Windows\CurrentVersion\Run\svchost
File Paths:       C:\Users\Public\svchost.exe

EMBEDDED RESOURCES
Resource 101:     Size=98304 Entropy=7.89 [!] Embedded PE detected
Resource 102:     Size=4096  Entropy=2.14 (configuration XML)

ASSESSMENT
Threat Level:     HIGH
Classification:   Dropper with process injection capabilities
Recommended:      Execute in sandbox, extract embedded PE for separate analysis

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/performing-static-malware-analysis-with-pe-studio of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • references/api-reference.md
  • scripts/agent.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Performing Static Malware Analysis With Pe Studio next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Performing Static Malware Analysis With Pe Studio compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Performing Static Malware Analysis With Pe Studio this skillmukul975/Anthropic-Cybersecurity-Skills34k—~3.3kAutomated safety check: PassApache-2.0
Firmware Security ReportsOrbitCurve/firmware-reverse-engineering216—~4.1kAutomated safety check: PassApache-2.0
Firmware Static AnalysisOrbitCurve/firmware-reverse-engineering216—~3.2kAutomated safety check: PassApache-2.0
APK Static Analysisdslsdzc/rev-skills135—~2kAutomated safety check: PassApache-2.0
Binary Reaiskillstore/marketplace4331 repos~2.6kAutomated safety check: PassNone
vphone600 Kernel Symbol AnalysisLakr233/vphone-cli15k—~530Automated safety check: PassMIT

Similar skills

  • Firmware Security Reports

    OrbitCurve/firmware-reverse-engineering

    Evidence-based security report generation for firmware assessments.

    216 GitHub stars~4.1k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Firmware Static Analysis

    OrbitCurve/firmware-reverse-engineering

    Systematic static analysis of ELF firmware binaries using command-line tools (file, strings, readelf, objdump, xxd).

    216 GitHub stars~3.2k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • APK Static Analysis

    dslsdzc/rev-skills

    Guides static analysis of an Android APK with jadx and apktool: reading the manifest, Java code, resources and permissions, and recognizing hardening or obfuscation.

    135 GitHub stars~2k tokensUpdated 5 days ago
    SecurityAuto-check passed
  • Binary Re

    aiskillstore/marketplace

    This skill should be used when analyzing binaries, executables, or bytecode to understand what they do or how they work.

    433 GitHub starsUsed in 1 repo~2.6k tokens
    SecurityAuto-check passed
  • Looks up symbols and addresses in vphone600 release and research kernel datasets, and cross-references XNU source, with findings that separate fact from inference.

    15k GitHub stars~530 tokensUpdated today
    SecurityAuto-check passed
  • Build, review, debug, reverse-engineer, and package WebHome injected extension scripts for FongMi/WebHome App WebView pages.

    1.7k GitHub stars~2.8k tokensUpdated yesterday
    SecurityAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo
  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Performing Static Malware Analysis With Pe Studio

What does Performing Static Malware Analysis With Pe Studio do?

Performs static analysis of Windows PE malware samples using PEStudio to examine file headers, imports, strings, and resources without executing the binary, identifying packing, anti-analysis…. Performing Static Malware Analysis With Pe Studio is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Performs static analysis of Windows PE malware samples using PEStudio to examine file headers, imports, strings, and resources without executing the binary, identifying packing, anti-analysis tricks, and malicious imports.

When should I use Performing Static Malware Analysis With Pe Studio?

Performing Static Malware Analysis With Pe Studio fits situations like: pre-execution triage of a suspicious Windows executable before sandbox detonation; tasks that involve Reverse engineering and malware; tasks that involve Static analysis and SAST.

How do I install Performing Static Malware Analysis With Pe Studio in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-static-malware-analysis-with-pe-studio -a claude-code`. Or copy the skill folder (skills/performing-static-malware-analysis-with-pe-studio in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/performing-static-malware-analysis-with-pe-studio in your project. Claude Code loads it when a task matches its description.

How do I install Performing Static Malware Analysis With Pe Studio in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-static-malware-analysis-with-pe-studio -a codex`. Or copy the skill folder (skills/performing-static-malware-analysis-with-pe-studio in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/performing-static-malware-analysis-with-pe-studio in your project. Codex loads it when a task matches its description.

Can I use Performing Static Malware Analysis With Pe Studio in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-static-malware-analysis-with-pe-studio -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/performing-static-malware-analysis-with-pe-studio, .gemini/skills/performing-static-malware-analysis-with-pe-studio, .github/skills/performing-static-malware-analysis-with-pe-studio and .opencode/skills/performing-static-malware-analysis-with-pe-studio in your project.

What does Performing Static Malware Analysis With Pe Studio need to run?

Going by SKILL.md and its folder, Performing Static Malware Analysis With Pe Studio needs Python for the scripts in its folder, the command-line tools its instructions call (curl, jq, python3, packer and pip) and credentials named VT_API_KEY. Our summary lists: Python 3; A credential in VT_API_KEY.

Does Performing Static Malware Analysis With Pe Studio access the network?

SKILL.md names 2 domains. In commands or code: virustotal.com; the agent is likely to contact it when it follows the instructions. As links in the text: winitor.com. This is read from the text; nothing was executed.

Is Performing Static Malware Analysis With Pe Studio safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Performing Static Malware Analysis With Pe Studio use?

Performing Static Malware Analysis With Pe Studio is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Performing Static Malware Analysis With Pe Studio use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 544 tokens, read only when the agent opens those files.

What are the alternatives to Performing Static Malware Analysis With Pe Studio?

Skills that share tags, products or a category with Performing Static Malware Analysis With Pe Studio: Firmware Security Reports (OrbitCurve/firmware-reverse-engineering, 216 stars), Firmware Static Analysis (OrbitCurve/firmware-reverse-engineering, 216 stars), APK Static Analysis (dslsdzc/rev-skills, 135 stars) and Binary Re (aiskillstore/marketplace, 433 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Performing Static Malware Analysis With Pe Studio?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.