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
noorqureshi/reverse-eng-deobfuscationIngeniería inversa y fuzzing

reverse-eng-deobfuscation

⁨Peel obfuscation off code until it's readable or callable — packed native binaries, minified/ obfuscated JavaScript, WebAssembly, and JS-VM-protected (JSVMP) bundles. Load when analysis is blocked by protection layers. Signals: high-entropy sections, a tiny import table, UPX headers, string-array/co⁩

v2026.10.14-ee0e0c53 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas

Instalar

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

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/reverse-eng-deobfuscation

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

FirmaFirmado, ed25519
1aOfBlsSlr…PmJFPLDA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete4d3996f2…d14c14c9
4d3996f2ed37…d808d14c14c91 archivo · ⁦2.0 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-deobfuscation@ee0e0c5

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

When it applies

reverse-eng-binary-triage or web-client-side-signing-bypass stalls because the code is protected: a packed executable, obfuscated JS whose logic you can't follow, a WASM blob doing the real work, or a JSVMP interpreter running custom bytecode. You need to reduce the protection enough to read the logic or call the function — no further.

Why it works

Obfuscation raises the cost of reading, it doesn't change what the code does — the real behavior is still there at runtime. So the shortest path is usually dynamic: let the code deobfuscate itself (unpack in memory, evaluate the string array) and capture the result, rather than statically undoing every transform.

Method

Peel only as many layers as the task needs; stop the moment the logic is legible or the function is callable.

  1. Native packers. Detect (high entropy, UPX! marker, one-section import stubs). For UPX, upx -d. For custom packers, run under a debugger to the original entry point (OEP) after the unpacking stub finishes, then dump the in-memory image and fix the imports.
  2. Obfuscated JS. Pretty-print first. Then resolve the common transforms: evaluate the string-array + rotator to substitute real names, constant-fold the arithmetic, and undo control-flow flattening (the while(true){switch(state)} dispatcher) by ordering the cases. AST tools (Babel) automate the mechanical passes; a sandbox (box-js) runs it safely to log what it builds.
  3. WebAssembly. wasm2wat to text; find exports and the imported JS bindings that feed it; hook the JS↔WASM boundary in DevTools to log inputs/outputs instead of reading every opcode.
  4. JSVMP (custom bytecode VM). Don't reimplement the VM — instrument it. Hook the dispatch loop / the handler that emits the result and log input → output, or lift only the handful of opcodes on the path you care about.
  5. Anti-debug. Neutralize debugger; traps (conditional breakpoint → never pause, or patch them out), timing checks, and integrity checks before they change behavior — but classify the divergence first so you don't "fix" the wrong thing.

Gotchas

  • Prefer dynamic to static — capturing self-deobfuscated output beats manually reversing every layer, especially for JSVMP and heavy packers.
  • Obfuscation ≠ the vulnerability. It's a means to reach the real bug (signing bypass, an endpoint, a secret) — don't report "the code is obfuscated".
  • Anti-debug can flip behavior when a debugger attaches — verify your deobfuscated path matches the real one (diff a known input/output).
  • Run unknown code sandboxed — a malicious bundle can act on execution.

Verify success

You can read the deobfuscated logic, or call the target function and reproduce its output for a known input — enough to hand back to reverse-eng-binary-triage, web-client-side-signing-bypass, or the exploit path.

References

UPX docs; Babel AST tooling; box-js; wasm2wat (WABT); notes on control-flow flattening & JSVMP.

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
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.10.14-ee0e0c513 nov 2026ee0e0c54d3996f2Firmada–

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