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

qiling

⁨Auth/lab ref: Qiling OS-layer binary emulation for PE/ELF/Mach-O/UEFI/shellcode with rootfs, syscall/API hooks, filesystem mapping, and runtime patching.⁩

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/qiling

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

FirmaFirmato, ed25519
ybTsuNbBEF…5FV96pAg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto835fe9da…74c86346
835fe9dabb10…f59074c863461 file · ⁦1.6 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/qiling@21cd568

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

Qiling sits between CPU-only emulation and full-system emulation: it loads executable formats, models OS APIs/syscalls, maps files, and lets the analyst hook behavior.

Use Qiling when

  • the target is PE, ELF, Mach-O, UEFI, DOS, shellcode, or a supported MCU-style sample
  • you need to fake files, registry keys, environment, argv, syscalls, or APIs
  • dynamic unpacking/decryption needs OS calls but not real hardware
  • anti-debug checks should be bypassed without a real debugger
  • you want instruction/basic-block/memory/API/syscall hooks

Prefer QEMU user-mode when you only need faithful Linux syscall forwarding. Prefer full-system or board emulation when kernel, drivers, interrupts, or peripherals are central.

Quick checks

bash
qltool run -f ./rootfs/bin/target --rootfs ./rootfs
qltool run -f ./sample.exe --rootfs ./rootfs/x8664_windows --json
qltool code --os linux --arch arm --format hex -f shellcode.hex

Rootfs matters. Missing DLLs, dylibs, registry hives, interpreters, or Linux userspace files are environment gaps, not necessarily target bugs.

Task-local harness pattern

When qltool is too small, create a temporary harness in the analysis workspace. Keep it minimal:

  • set argv, rootfs, env, archtype, ostype, endian, and Thumb mode explicitly
  • map only required host files into the guest namespace
  • hook one syscall/API/address at a time
  • log arguments and return values before patching them
  • stop at a clear success signal or timeout

Do not build a large reusable framework before one dynamic question is proven.

Hooking decisions

Missing behavior Good Qiling response
file path missing map or create the exact path observed in logs
registry/config missing provide minimal key/value expected by the target
unsupported API/syscall hook only if it is environmental, not the behavior under study
decryption routine hook output buffer or stop after the routine
anti-debug/time/randomness patch return value and label it as an analysis fake
network API log parameters first; emulate response only when protocol content is not the question

Evidence

  • command or harness options
  • rootfs/source of OS assets
  • list of hooks and fake return values
  • stdout/stderr/log output
  • dumped memory/config after runtime transformation
  • reason Qiling is sufficient or why escalation is needed

Common boundaries

  • Qiling is not a complete OS or hardware simulator.
  • Some syscalls/APIs are unimplemented; that is a normal pivot point.
  • Windows and macOS targets often need legally obtained runtime assets from matching systems.
  • CPU-level success under Qiling does not prove kernel, driver, or peripheral behavior.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
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 202621cd568835fe9daFirmata–

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