agentsclimarketplace
Sign in

Analyzing rust malware internals

Skill meltedinhex/analyst-ai-pack/skills/analyzing-rust-malware-internals

Analyzes Rust-compiled malware by detecting the Rust toolchain signature, demangling Rust v0/legacy symbol names, and identifying crate dependencies from embedded paths. Activates for requests to analyze Rust malware, demangle Rust symbols, or identify a Rust binary build and its crates.From its SKILL.md

Install
npx -y skills add meltedinhex/analyst-ai-pack --skill analyzing-rust-malware-internals

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, 440 tokens by cl100k_base, as published. Nobody here has run it

Analyzing Rust Malware Internals

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

What ships with it: 3 files

4.3 KB alongside SKILL.md, 1 of them executable

references/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.