Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/analyzing-rust-malware-internalsMalware and ransomware analysis

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-internals

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
Cx+aa8iNnm…YARoCpCw==The CLI checks the SHA-256 and the signature before it writes a file.
Package0e5fcc8d…d228570b
0e5fcc8d2a58…6083d228570b4 files · ⁦3.2 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-rust-malware-internals@da7600a

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

bash
python scripts/analyst.py info sample.bin

Looks 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.md for the analyzer/demangler.
  • Rust v0 mangling RFC and ATT&CK T1027 (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a0e5fcc8dSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login