Menu

Individual skill

analyzing-rust-binaries

0upvotes

Reverse engineer Rust binaries — demangling legacy and v0 symbol schemes, recognizing monomorphized generics, Result and Option control flow, trait object vtable dispatch, and panic-site strings that leak source paths and crate names. Use when a binary contains rustc version strings, core::panicking, or _ZN/_R mangled symbols, when a stripped binary is unexpectedly large, or when analyzing Rust malware or a Rust service.

secskills-core/skills/analyzing-rust-binaries/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
188
Repository last updated
Sep 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Analyzing Rust Binaries

Rust binaries are large, statically linked, and full of inlined generic code —
but they leak more than most people expect. Panic sites embed the source file
path and line, symbols carry crate and module structure, and the standard
library's formatting machinery is instantly recognizable. The job is knowing
which parts are yours and which are the 90% that is `core`, `alloc`, and
vendored crates.

## When to Use

- `strings` shows `rustc version`, `core::panicking`, `/rustc/<hash>/library/`
- Symbols begin with `_ZN...17h<hex>E` (legacy) or `_R` (v0 mangling)
- A stripped binary is 3–30 MB with minimal dynamic imports