Individual skill

reverse-eng-go-rust

Reverse stripped Go and Rust binaries — recover symbols from pclntab/moduledata and panic metadata, then navigate language-specific idioms. Load when a stripped ELF/PE/Mach-O shows Go or Rust runtime residue. Signals: "go.buildid", "runtime.main" / "main.main", "panic:" or "rust_begin_unwind" strings, /rustc/ or src/*.rs paths, huge static binary with no symbols, Go malware, a Rust release build.

skills/reverse-engineering/reverse-eng-go-rust/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

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 11, 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)
27
Repository last updated
Oct 14, 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

# Go / Rust binary reversing

## When it applies
You have a stripped binary in scope (`tradecraft-scope-roe`, `scope.txt`) and triage
(`reverse-eng-binary-triage`) shows Go or Rust residue — a Go malware sample, a Rust release
build, a Go-compiled red-team tool. Generic decompilation drowns you in runtime code; these
languages carry enough metadata to rebuild the symbol map first.

## Why it works
Both toolchains ship binaries that are mostly runtime, but both embed rich metadata: Go keeps the
pclntab (function names, file:line, type info) even when the symbol table is stripped, and Rust
leaks panic strings with full source paths. Recovering that metadata turns an anonymous blob back
into named functions, and the runtime residue itself fingerprints the language and version.
Back to top