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
aeondave/unicornReverse engineering e fuzzing

unicorn

⁨Auth/lab ref: Unicorn Engine CPU-only emulation for shellcode, decryptors, custom VM handlers, instruction tracing, memory hooks, and register-level experiments.⁩

v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 StelleMITsincronizzato 11 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/unicorn

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

FirmaFirmato, ed25519
1WKWf+w6Wc…AAZvtFBA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto0d1ceacb…cce63b7c
0d1ceacb0277…0769cce63b7c1 file · ⁦1.4 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/offensive-tools/rev/unicorn@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

Unicorn is a CPU emulator. It is the right tool when you can define memory, registers, and stop conditions yourself.

Use Unicorn when

  • the target is shellcode, a decoder, checksum loop, custom VM handler, crypto primitive, or small boot stub
  • OS behavior would be noise
  • you know or can infer load address, entry address, mapped memory, stack, registers, and inputs
  • memory/register hooks are the evidence you need

Do not use Unicorn as a shortcut for real userland execution. If the target needs syscalls, files, dynamic linking, registry, interrupts, or hardware peripherals, use Qiling, QEMU, or Renode instead.

Setup checklist

  • architecture, mode, endian, ARM/Thumb state
  • code mapping address and permissions
  • stack address and size
  • input buffers and output buffers
  • initial registers and calling convention
  • imported function stubs or syscall stop points
  • maximum instruction count or address stop

Hook strategy

Hook Use
basic block coverage, control-flow sketch, custom VM dispatch
instruction exact trace, self-modifying code, privileged instruction stop
memory read/write watchpoints, decrypted output, MMIO discovery
unmapped memory identify missing mapping, import thunk, stack growth, bad pointer
interrupt/syscall stop or fake external behavior

Keep hooks narrow. Broad instruction hooks over large regions can make emulation painfully slow.

Good targets

  • XOR/RC4/AES wrapper that fills a plaintext buffer
  • password checker inner loop
  • architecture-specific shellcode decoder
  • VM bytecode dispatcher over a byte array
  • bare-metal reset stub before first peripheral wait
  • opaque predicate or anti-debug gadget

Bad targets

  • dynamically linked application with many libc calls
  • Windows or macOS binary that needs real APIs
  • Linux service that opens files, forks, listens on sockets, or uses /proc
  • MCU firmware stuck in timer/UART/GPIO MMIO loops unless those reads/writes are stubbed deliberately
  • kernel boot, drivers, or interrupt-heavy RTOS behavior

Evidence

  • initial register/memory state
  • hook outputs and stop reason
  • memory dump of transformed buffers
  • branch or address coverage proving the target path
  • exact stubs used for external calls

State clearly that the proof is CPU-level unless OS or board behavior was validated elsewhere.

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.11.13-21cd56813 nov 202621cd5680d1ceacbFirmata–

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