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
dariushoule/tracealyzerDFIR y threat hunting

tracealyzer

⁨Trace execution (into or over calls) for N steps or until a condition, then analyze the recorded instruction log⁩

v2026.3.13-0409f533 instalaciones+3 en 7 días210 EstrellasMITsincronizado hace 11 horas

Instalar

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

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install dariushoule/tracealyzer

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

FirmaFirmado, ed25519
VOrv+UiX9e…PzyhfjCA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete01677937…a9661e0c
0167793710d9…79a3a9661e0c1 archivo · ⁦1.8 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/dariushoule/x64dbg-skills/tree/main/skills/tracealyzer@0409f53

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

Trace debuggee execution — stepping into or over calls — for a specified number of instructions or until a condition is met. The full instruction log is captured to a file and then analyzed.

Instructions

Follow these steps exactly:

1. Verify debugger connection

Call mcp__x64dbg__get_debugger_status to confirm the debugger is connected and a debuggee is loaded and paused. If it is running, call mcp__x64dbg__pause. If no debuggee is loaded, tell the user and stop.

2. Gather trace parameters

Ask the user for the following if not already provided:

  • Trace mode: trace into calls or trace over calls (default: over)
  • Stop condition — one of:
    • A maximum number of instructions (e.g. 1000)
    • An x64dbg expression that stops when true (e.g. cip == 0x7FF6A0001000, rax != 0)
    • Both (whichever triggers first)

If the user provides a symbol or address for the stop condition, resolve it with mcp__x64dbg__eval_expression and build the break_condition expression (e.g. cip == <resolved_addr>).

When the user only specifies a step count N and no explicit break condition, use break_condition 0 (never true — the trace runs until max_steps is hit).

3. Capture starting context

Call mcp__x64dbg__get_all_registers and mcp__x64dbg__disassemble at the current instruction pointer to record the starting state. Note the starting address.

4. Run the trace

Prepare the output log path: ./traces/trace_<timestamp>.log (create the traces directory if it doesn't exist via Bash).

Call the appropriate trace tool (mcp__x64dbg__trace_into or mcp__x64dbg__trace_over) with:

Parameter Value
break_condition The user's condition, or 0 if only a step count was given
max_steps The user's step count, or 50000 if only a condition was given
log_text `{p:cip} {i:cip}
log_file The output log path from above
wait_timeout Scale with max_steps — use max(60, max_steps // 500) seconds

5. Read and analyze the trace log

Read the trace log file. The log contains one line per executed instruction in the format:

text
<address> <disassembly> | Label=<label> Comment=<comment>

Ignore when Labels or Comments say [Formatting Error], it just means there is no label or comment at that instruction.

Analyze the trace and present a summary to the user:

  • Trace overview: total instructions executed, start address → end address, trace mode used
  • Execution flow: describe the high-level behavior — what the code did, which functions were called, loops observed, and notable control-flow patterns
  • Hot spots: addresses or regions that appear most frequently (loops, repeated calls)
  • Key observations: interesting register manipulations, memory accesses, syscalls, API calls, string operations, or anything else that stands out

Use mcp__x64dbg__get_symbol to resolve notable addresses to symbol names where possible.

If the trace log is very large (>2000 lines), read it in chunks and summarize progressively.

6. Follow-up actions

After presenting the summary, ask the user if they would like any follow-up actions such as:

  • Annotate: add comments/labels in x64dbg at key addresses using mcp__x64dbg__set_comment / mcp__x64dbg__set_label
  • Deeper analysis: re-trace a specific sub-region, or focus on a particular function
  • Deobfuscation: identify and explain obfuscated patterns found in the trace
  • Export: the trace log is already saved to disk at the path from step 4

Archivos de esta versión

Permisos

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

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

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

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.3.13-0409f5313 nov 20260409f5301677937Firmada–

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