Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/reverse-engineering-binaries-with-ghidraReverse engineering and fuzzing

reverse-engineering-binaries-with-ghidra

⁨Uses Ghidra to disassemble and decompile a binary, navigate to key routines via⁩

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/reverse-engineering-binaries-with-ghidra

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
bBuO78+NOA…GTiglxAA==The CLI checks the SHA-256 and the signature before it writes a file.
Packagee089479b…fd2416db
e089479b2eb8…88dffd2416db4 files · ⁦3.3 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/reverse-engineering-binaries-with-ghidra@da7600a

When to Use

  • Static/dynamic triage has identified functionality that needs code-level understanding.
  • You need to reverse a C2 protocol, decryption routine, or custom obfuscation.
  • You want to extract hardcoded config (C2, keys, campaign IDs) from compiled code, or automate extraction across many samples via headless scripts.

Do not use Ghidra as a first step for unknown samples — triage statically and behaviorally first, and unpack before decompiling a packed binary.

Prerequisites

  • Ghidra 11.x with JDK 17+.
  • An isolated analysis host.
  • Familiarity with x86/x64 (or the target arch) and OS API conventions.
  • The sample unpacked (decompiling packed code wastes effort).

Safety & Handling

  • Ghidra performs static analysis and does not run the sample, but still work in the lab.
  • Treat any dumped/derived payloads as live samples.

Workflow

Step 1: Import and auto-analyze

Create a project, import the binary (Ghidra detects PE/ELF/Mach-O and arch), and run auto-analysis with default analyzers.

Step 2: Navigate to interesting code

Start from imports (Symbol Tree) and strings (Defined Strings). Cross-reference (X) from a suspicious API or string to its callers to reach the relevant function quickly.

text
VirtualAlloc/WriteProcessMemory -> injection logic
InternetOpen/WinHttp*           -> C2
CryptEncrypt / custom XOR loops -> crypto/config decode

Step 3: Annotate the decompiler output

Retype variables, rename functions, and add comments as you understand the code. Good naming turns the decompiler into readable pseudo-C and compounds across a session.

Step 4: Automate with headless scripts

For repeatable extraction, run Ghidra headless with a post-script. The bundled Python uses analyzeHeadless to export functions/strings to JSON:

bash
python scripts/analyst.py headless --ghidra /opt/ghidra --bin sample.bin --out out.json

Step 5: Extract the target artifact

Recover the C2 string, key, or config and validate it against dynamic observations.

Validation

  • Renamed/retyped routines produce coherent pseudo-C consistent with observed behavior.
  • Extracted config (C2/keys) matches what the sample uses at runtime.
  • Headless export reproduces the interactive findings.

Pitfalls

  • Decompiling packed/obfuscated code — unpack first or the output is meaningless.
  • Trusting decompiler types blindly; verify against the disassembly for crypto/pointer logic.
  • Ignoring TLS callbacks/constructors that run before the entry point.

References

  • See references/api-reference.md for the headless wrapper.
  • Ghidra documentation and API (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600ae089479bSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login