analyzing-golang-malware-internals
Analyzes Go-compiled malware by recovering function names from the pclntab, detecting
v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/analyzing-golang-malware-internalsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package79870192…0700ecdd
79870192cc90…56490700ecdd4 files · 3.0 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-golang-malware-internals@da7600a
On this page
When to Use
- You have a Go-compiled binary (often large, statically linked) and standard symbol recovery fails because user symbols are stripped.
- You need function names from the pclntab, the Go version, and embedded package/module paths.
Do not use this for non-Go binaries — confirm the Go build signature first. This skill reads the binary statically and executes nothing.
Prerequisites
- The Go binary (read inertly).
Safety & Handling
- Read bytes statically; treat strings as untrusted data.
Workflow
Step 1: Confirm it is Go and get the version
python scripts/analyst.py info sample.binLooks for the Go build ID, the go1.x version string, and runtime. references.
Step 2: Recover function names from pclntab
The pclntab (preceded by a magic like \xfb\xff\xff\xff/\xf0\xff\xff\xff across Go versions)
contains function name strings; extract main.*, package-qualified, and runtime.* names.
Step 3: Enumerate package paths
List embedded import/module paths (github.com/..., vendored deps) to fingerprint capabilities
and third-party libraries.
Step 4: Map and document
Map suspicious packages (networking, crypto, exec) to behavior and ATT&CK.
Validation
- The Go build signature/version is confirmed before deeper parsing.
- Recovered names include plausible
main.*/package-qualified functions. - Package paths are real module paths, not random strings.
Pitfalls
- pclntab magic differs across Go versions; try the known set.
- Obfuscators (garble) rename symbols and strip build info — names may be hashed.
- Confusing vendored library code with the author's
mainpackage.
References
- See
references/api-reference.mdfor the analyzer. - Go pclntab/buildinfo references (linked in frontmatter).
Files in this version
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.3 KB
- analyst.py2.3 KB
- LICENSE340 B
- SKILL.md2.7 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- 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 |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 79870192 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask 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