analyzing-rust-malware-internals
Analyzes Rust-compiled malware by detecting the Rust toolchain signature, demangling
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-rust-malware-internalsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package0e5fcc8d…d228570b
0e5fcc8d2a58…6083d228570b4 files · 3.2 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-rust-malware-internals@da7600a
On this page
When to Use
- You have a Rust-compiled binary and need to confirm the toolchain, demangle symbol names, and enumerate crate dependencies.
- Standard analysis is hampered by Rust's name mangling and large static linking.
Do not use this for non-Rust binaries — confirm the Rust signature first. This skill reads the binary statically and executes nothing.
Prerequisites
- The Rust binary (read inertly).
Safety & Handling
- Read bytes statically; treat strings as untrusted.
Workflow
Step 1: Confirm Rust and toolchain
python scripts/analyst.py info sample.binLooks for rustc/cargo markers, the rust panic/unwind strings, and embedded source paths
(/rustc/<hash>/library/..., ~/.cargo/registry/...).
Step 2: Demangle symbol names
Detects v0 (_R...) and legacy (_ZN...17h<hash>E) mangled symbols and demangles them to readable
paths.
Step 3: Enumerate crates
Extract crate names/versions from .cargo/registry/src/.../<crate>-<ver>/ paths to fingerprint
capabilities (e.g., reqwest, tokio, aes, winapi).
Step 4: Map and document
Map notable crates to behavior and ATT&CK.
Validation
- The Rust toolchain signature is confirmed before demangling.
- Demangled names are readable module paths (not still-mangled).
- Crate names/versions are plausible registry entries.
Pitfalls
- Mixing v0 and legacy mangling in one binary — handle both.
- Stripped binaries where only registry path strings remain.
- Static crates inflating the symbol set; focus on the author's crate/
main.
References
- See
references/api-reference.mdfor the analyzer/demangler. - Rust v0 mangling RFC and ATT&CK T1027 (linked in frontmatter).
Files in this version
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.7 KB
- analyst.py2.7 KB
- LICENSE340 B
- SKILL.md2.6 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | Yes | Yes |
| 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 | 0e5fcc8d | 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 Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask 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