Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
meltedinhex/reverse-engineering-binaries-with-ghidraEngenharia reversa e fuzzing

reverse-engineering-binaries-with-ghidra

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

v1.0.03 instalações+3 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/reverse-engineering-binaries-with-ghidra

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
bBuO78+NOA…GTiglxAA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacotee089479b…fd2416db
e089479b2eb8…88dffd2416db4 arquivos · ⁦3.3 KB⁩
VarreduraMédio2 achados
  • Script executável junto com a skillscripts/analyst.py
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/reverse-engineering-binaries-with-ghidra@da7600a

Este item ainda não foi escrito no seu idioma, então aparece em English.

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).

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosSimSim
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaArquivo · Script executável junto com a skillscripts/analyst.py
  2. 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ãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v1.0.013 de nov. de 2026da7600ae089479bAssinada–

Pergunte 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. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login