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" string
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/reverse-eng-go-rustWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagece357694…a2a59619
ce35769463e5…e720a2a596191 file · 2.2 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-go-rust@ee0e0c5
On this page
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.
Method
- Fingerprint the language.
- Go:
stringsforgo.buildid,runtime.,src/.../*.gopaths,Go buildinf. - Rust:
stringsforrust_begin_unwind,panicked at,/rustc/<hash>/library/...paths, crate names insrc/*.rspaths.
- Go:
- Go: recover symbols from pclntab. Run GoReSym (
GoReSym -t target) or redress to parse pclntab/moduledata → function names, types, package list; import the output into IDA/Ghidra (Go helper plugins apply it as names/types). Then anchor atruntime.main→main.mainand work outward into themain.*package — skip theruntime.*/crypto/*/net/httplibrary code except to note which libraries are linked (crypto and net paths hint at C2 and key handling). - Rust: drive from panic strings. Each
panicked at '...', src/foo.rs:LINE:COLstring is a file:line anchor — xref it to land inside real logic. CollectOption/Resultunwrap sites the same way. - Read idioms, not just code.
- Go strings are (pointer, length) pairs — not NUL-terminated; slices are (ptr, len, cap); interfaces are (itab, data). A "two arguments" call passing a string is really one string.
- Rust generics explode one function into many monomorphized copies — don't analyze each; follow string xrefs to the copy that matters. Async (tokio) compiles to state machines; reconstruct flow via cross-references, not linear reading.
- Dynamic confirms. gdb and Frida both work, but mind Go's scheduler: goroutines hop OS threads, so break on a string usage (log line, config key, crypto input) rather than chasing a thread. Config/log strings are the best breakpoint anchors in both languages.
Gotchas
- Packed first, language second — UPX et al. hide the pclntab; unpack before GoReSym
(
reverse-eng-deobfuscation). - Malware corrupts moduledata (zeroed magic, moved pclntab) specifically to break GoReSym — locate pclntab by its magic bytes in the section and repair, or fall back to string-driven analysis.
- Don't get lost in the runtime — most functions in the binary are library code. If a function has no path to attacker input or secrets, move on.
- Stripped Rust gives almost nothing back — panic strings and crate paths are the map; rename functions as you identify them or the picture doesn't survive.
Verify success
Key functions are renamed (or you hold an equivalent offset→purpose map), the language/runtime evidence is recorded (build ID, compiler version, linked packages), and you can state where attacker-controlled input and the interesting crypto/network logic live.
References
GoReSym & redress documentation; Go pclntab/moduledata format writeups; Rust panic ABI notes.
Portions adapted from reverse-skill by zhaoxuya520, MIT License.
Files in this version
- SKILL.md4.2 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- 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 |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | ce357694 | Signed | – |
More from NoorQureshi
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk 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