analyzing-rich-header-and-compiler-artifacts
Analyzes the PE Rich header and related compiler artifacts to fingerprint the build
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/analyzing-rich-header-and-compiler-artifactsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package2de67168…46a8cd06
2de67168395d…147346a8cd064 files · 2.9 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-rich-header-and-compiler-artifacts@da7600a
On this page
When to Use
- You have a Windows PE and want to fingerprint its build toolchain (compiler/linker product IDs and build numbers) from the Rich header.
- You are clustering samples by toolchain or detecting Rich-header tampering/forgery.
Do not use the Rich header as definitive attribution — it can be copied or stripped. This skill reads the PE statically and executes nothing.
Prerequisites
- The PE sample (read inertly).
Safety & Handling
- Read bytes statically; treat the sample as malicious data.
Workflow
Step 1: Parse and decode the Rich header
python scripts/analyst.py rich sample.exeLocates the Rich marker, recovers the XOR key (the DWORD after Rich), decodes the DanS-
prefixed entries, and lists (product_id, build_id, use_count) tuples.
Step 2: Fingerprint the toolchain
Map product IDs to compiler/linker products and build numbers to identify the Visual Studio version(s) used.
Step 3: Compute a clustering hash
Hash the decoded Rich entries to produce a toolchain fingerprint for grouping related samples.
Step 4: Check for inconsistencies
Compare the Rich-derived linker version against the PE optional-header linker version; mismatches suggest tampering or a copied header.
Validation
- The XOR key correctly decodes the
DanSsignature at the start of the block. - Decoded entries have plausible product IDs and use counts.
- The toolchain fingerprint is reproducible across identical builds.
Pitfalls
- Samples with no Rich header (non-MSVC toolchains, stripped headers).
- Forged Rich headers copied from a benign binary.
- Confusing the Rich checksum/key handling and misdecoding entries.
References
- See
references/api-reference.mdfor the parser. - PE format documentation (linked in frontmatter).
Files in this version
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.6 KB
- analyst.py2.6 KB
- LICENSE340 B
- SKILL.md2.7 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 | 2de67168 | 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