Analyzing Golang Malware With Ghidra
Reverse-engineer suspicious Go binaries in Ghidra and document C2 indicators, dependencies, and defensive recommendations.
Overview
Analyzing Golang Malware with Ghidra is an agent skill for the Ship phase that structures Go binary reverse-engineering reports with recovered functions, C2 indicators, and remediation recommendations.
Install
npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill analyzing-golang-malware-with-ghidraWhat is this skill?
- Report template for SHA-256, Go version, arch, stripped, and garble obfuscation flags
- Function recovery buckets: main, networking, crypto, os/exec, and third-party modules
- C2 infrastructure table for URLs, IPs, and domains extracted from the sample
- Dependency module mapping and actionable blocklist plus YARA guidance
- Oriented to amd64, arm64, and 386 Go malware artifacts
- 5 function recovery categories in the report template (main, networking, crypto, os/exec, third-party)
Adoption & trust: 1 installs on skills.sh; 14.9k GitHub stars; 1/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You have a suspicious Go binary and no consistent way to document architecture, obfuscation, dependencies, and C2 in a shareable security report.
Who is it for?
Security-literate solo builders or small teams triaging Go malware samples in Ghidra during incident response or supply-chain review.
Skip if: Beginners seeking automatic one-click remediation, or founders who only need routine dependency CVE scanning without reverse engineering.
When should I use this skill?
You are reverse-engineering a Go malware or suspicious Go binary in Ghidra and need a standardized analysis and C2 reporting format.
What do I get? / Deliverables
You produce a completed Go malware analysis report with indicator tables and prioritized recommendations to block C2, draft YARA, and watch for similar build artifacts.
- Go malware analysis report with sample metadata
- C2 and dependency indicator tables
- Blocking, YARA, and monitoring recommendations
Recommended Skills
Journey fit
Malware triage belongs in ship/security when you are validating third-party or supply-chain binaries before or after release—not in casual idea research. The skill produces structured security findings (functions, C2, YARA follow-ups) aligned with pre-ship and incident review workflows.
How it compares
Use for Ghidra-centric Go malware documentation—not for generic SAST scanners or application penetration-test checklists.
Common Questions / FAQ
Who is analyzing-golang-malware-with-ghidra for?
Operators and security-curious builders who analyze Go executables in Ghidra and need a repeatable report format for C2 and function recovery.
When should I use analyzing-golang-malware-with-ghidra?
During ship/security reviews of suspicious binaries, after a supply-chain scare, or in operate/incident workflows when documenting Go malware for blocking and detection.
Is analyzing-golang-malware-with-ghidra safe to install?
The skill describes analysis of potentially malicious samples; only run in isolated lab environments and review the Security Audits panel on this Prism page before install.
SKILL.md
READMESKILL.md - Analyzing Golang Malware With Ghidra
# Go Malware Analysis Report ## Sample Information | Field | Value | |-------|-------| | SHA-256 | | | File Size | | | Go Version | | | Architecture | amd64 / arm64 / 386 | | Stripped | Yes / No | | Obfuscated | Yes (garble) / No | ## Recovered Functions | Category | Count | Key Functions | |----------|-------|---------------| | main | | | | networking | | | | crypto | | | | os/exec | | | | third-party | | | ## Dependencies | Module | Purpose | |--------|---------| | | | ## C2 Infrastructure | Indicator | Type | Value | |-----------|------|-------| | | URL / IP / Domain | | ## Recommendations 1. Block identified C2 infrastructure 2. Create YARA rule for unique Go function signatures 3. Monitor for similar Go binary compilation artifacts Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designat