Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/reverse-eng-deobfuscationReverse engineering e 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 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

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

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
1aOfBlsSlr…PmJFPLDA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto4d3996f2…d14c14c9
4d3996f2ed37…d808d14c14c91 file · ⁦2.0 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-deobfuscation@ee0e0c5

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: 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.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.10.14-ee0e0c513 nov 2026ee0e0c54d3996f2Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login