performing-static-pe-analysis
Extracts structure and indicators from a Windows PE file without executing it:
v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/performing-static-pe-analysisWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagee5a1e68b…87ce1f6f
e5a1e68bd110…e1bf87ce1f6f4 files · 4.1 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/performing-static-pe-analysis@da7600a
On this page
When to Use
- You have a Windows executable or DLL and need to infer its capabilities before (or instead of) detonation.
- You want to assess packing, suspicious imports, timestamps, and embedded resources.
- You are gathering features for YARA authoring or detection.
Do not use import tables alone to conclude behavior — packed samples hide imports until runtime. If imports are sparse and entropy is high, move to unpacking.
Prerequisites
pefile(pip install pefile) and optionallycapa/PEStudio for deeper capability ID.- The sample in neutralized form inside the lab.
Safety & Handling
- Static only: parse the file, never run it. Keep the neutralized extension.
Workflow
Step 1: Parse headers and metadata
python scripts/analyst.py analyze sample.binNote the compile timestamp (often forged), subsystem (GUI/console), machine type (x86/x64), and whether it is a DLL.
Step 2: Review sections and entropy
Per-section entropy reveals packing. A tiny .text plus a huge high-entropy section, or
non-standard section names (UPX0, .themida), indicate a packer:
.text entropy 6.4 (normal code)
UPX1 entropy 7.95 (packed)Step 3: Classify imports
Group imported APIs into behavioral buckets:
Injection : VirtualAllocEx, WriteProcessMemory, CreateRemoteThread [T1055]
Network : InternetOpen, HttpSendRequest, WinHttpConnect [T1071]
Crypto : CryptEncrypt, CryptAcquireContext [T1486]
Persistence: RegSetValueEx, CreateService [T1547/T1543]A sample importing only LoadLibrary/GetProcAddress is resolving APIs dynamically — a
packing/evasion tell.
Step 4: Inspect resources and strings
Look for embedded PEs in resources (droppers), config blobs, and notable strings (URLs, mutex names, paths).
Step 5: Check signing
Verify the Authenticode signature: unsigned, self-signed, or revoked certificates are suspicious for software claiming to be legitimate.
Validation
- Section entropy and import counts agree (packed → few imports + high entropy).
- Suspicious import buckets correspond to plausible behavior.
- Embedded PE detection is confirmed by an
MZ/PEheader inside a resource.
Pitfalls
- Trusting the compile timestamp as a real build date — it is trivially forged.
- Concluding "benign" because imports look ordinary; the import table may be a stub for a packed payload.
- Ignoring TLS callbacks, which can run code before the entry point.
References
- See
references/api-reference.mdfor the analyzer and import classification map. - Microsoft PE Format spec and pefile (linked in frontmatter).
Files in this version
references/11.4 KB
- api-reference.md1.4 KB
scripts/14.1 KB
- analyst.py4.1 KB
- LICENSE340 B
- SKILL.md3.5 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | e5a1e68b | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login