Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
meltedinhex/debugging-malware-with-x64dbgIngeniería inversa y fuzzing

debugging-malware-with-x64dbg

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

v1.0.02 instalaciones+2 en 7 días24 EstrellasApache-2.0sincronizado hace 10 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/debugging-malware-with-x64dbg

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
249g1at6BB…V4e7rxDQ==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquetece372524…bf8b6490
ce372524240b…10b7bf8b64904 archivos · ⁦3.5 KB⁩
EscaneoMedio2 hallazgos
  • Script ejecutable incluido con la skillscripts/analyst.py
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/debugging-malware-with-x64dbg@da7600a

Esta entrada todavía no está escrita en tu idioma, así que aparece en 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).

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosSíSí
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
  2. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v1.0.013 nov 2026da7600ace372524Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login