Skip to content
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 and 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 installs+3 in 7 days39 StarsMITsynced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

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

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
ybTsuNbBEF…5FV96pAg==The CLI checks the SHA-256 and the signature before it writes a file.
Package835fe9da…74c86346
835fe9dabb10…f59074c863461 file · ⁦1.6 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/rev/qiling@21cd568

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.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd568835fe9daSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login