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 instalações+3 em 7 dias27 EstrelasMITsincronizado há 22 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/reverse-eng-go-rustGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacotece357694…a2a59619
ce35769463e5…e720a2a596191 arquivo · 2.2 KBVarreduraBaixo1 achado
- Links para domínios externos
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-go-rust@ee0e0c5
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
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.
Arquivos desta versão
- SKILL.md4.2 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Não | Não |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 de nov. de 2026 | ee0e0c5 | ce357694 | Assinada | – |
Mais de NoorQureshi
Tudo deste publicadorMais em Engenharia reversa e fuzzing
Ver a categoriaPergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login