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/debugging-malware-with-x64dbgEngenharia reversa e fuzzing

debugging-malware-with-x64dbg

⁨Uses x64dbg to dynamically debug Windows malware: setting strategic breakpoints⁩

v1.0.02 instalações+2 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/debugging-malware-with-x64dbg

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

AssinaturaAssinado, ed25519
249g1at6BB…V4e7rxDQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacotece372524…bf8b6490
ce372524240b…10b7bf8b64904 arquivos · ⁦3.5 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/debugging-malware-with-x64dbg@da7600a

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

When to Use

  • You need to observe a sample's runtime behavior at the instruction level on Windows.
  • You are manually unpacking, decrypting strings, or reaching code guarded by anti-analysis.
  • You want to dump a payload from memory after it is decoded but before it is hidden.

Do not use a debugger on a host you care about — debug only inside the isolated victim VM, and revert the snapshot after.

Prerequisites

  • x64dbg (and the matching x32/x64 build for the sample's bitness) inside the victim VM.
  • A clean snapshot; the lab's simulated internet.
  • Familiarity with Windows APIs commonly used by malware.

Safety & Handling

  • The sample executes under the debugger; this is detonation. Stay in the isolated VM.
  • Revert the snapshot after the session; treat memory dumps as live samples.

Workflow

Step 1: Set strategic API breakpoints

Rather than stepping from the entry point, break on APIs that mark interesting moments:

text
VirtualAlloc / VirtualProtect  -> unpacking buffer about to be written/executed
CreateProcessInternalW         -> process hollowing target
WriteProcessMemory             -> injection payload in a register/buffer
CryptDecrypt / lstrcpy         -> decoded data available
ResumeThread                   -> hollowed process about to run

Use bp VirtualAlloc then inspect the return value (allocated base) on return.

Step 2: Step through unpacking

Run to the allocation, set a memory breakpoint on the new region, and continue until the unpacker writes and jumps to it. The tail jump to OEP marks the unpacked entry.

Step 3: Dump at the right moment

When the payload is decoded in memory (e.g. after VirtualProtect makes it executable), dump the region with Scylla/the dump plugin and fix the import table for the unpacked PE.

Step 4: Defeat simple anti-debugging

Patch or skip checks like IsDebuggerPresent, PEB BeingDebugged, and timing checks (see the anti-debugging skill). Set the return value to evade detection rather than removing the call.

Step 5: Record breakpoints and notes

Save a breakpoint plan and observations. The bundled script generates an x64dbg command script of API breakpoints to bootstrap a session.

bash
python scripts/analyst.py breakpoints --preset unpacking > bp.txt

Validation

  • The dumped region is a valid PE (MZ/PE headers) and disassembles to real code.
  • API breakpoints fire in an order consistent with unpacking/injection.
  • Patched anti-debug checks no longer alter the execution path.

Pitfalls

  • Stepping blindly from the entry point instead of using API breakpoints — slow and easy to get lost.
  • Dumping too early (still encrypted) or too late (already executed/freed).
  • Removing anti-debug calls entirely, which can break control flow; prefer faking the result.

References

  • See references/api-reference.md for the breakpoint-script generator.
  • x64dbg and Windows API documentation (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 2026da7600ace372524Assinada–

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