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/one-gadgetReverse engineering and fuzzing

one-gadget

⁨Auth/lab ref: libc gadget finder for `execve`-style code execution opportunities under known register and stack constraints.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 Starssynced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

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

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

SignatureSigned, ed25519
XZ6mjdUb1G…fh+aPABw==The CLI checks the SHA-256 and the signature before it writes a file.
Package4438c90e…0d33b63c
4438c90e5c54…c7c70d33b63c1 file · ⁦1.1 KB⁩
ScanMedium1 finding
  • No license found
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/rev/one-gadget@21cd568

Fast libc post-leak shortcut finder. Great when it works, humbling when constraints bite back.

When to use one-gadget

Use one-gadget when you need to:

  • turn a libc base leak into candidate execve offsets
  • compare several constraint-heavy RCE options quickly
  • decide whether a short stack/register fix-up beats a full custom chain

Quick Start

bash
# Enumerate candidate gadgets in libc
one_gadget ./libc.so.6

# Show more gadgets and constraints
one_gadget -l 2 ./libc.so.6

# Raw offsets only
one_gadget --raw ./libc.so.6

Practical Workflow

  1. Identify the exact libc or a trustworthy build match.
  2. Compute the libc base from your leak.
  3. Run one_gadget on that libc file.
  4. Read the printed constraints carefully.
  5. Validate stack, registers, and writable memory in gdb before betting the exploit on one offset.

Practical Notes

  • Constraints are the whole game: rsp contents, rax == NULL, or writable memory requirements often decide feasibility.
  • one-gadget is best after you already solved ASLR for libc.
  • Keep a normal ROP fallback path ready; many stable exploits start with one-gadget as a probe, not as the final design.

Caveats

  • A valid offset does not imply a reachable or repeatable exploit path.
  • Version drift between local and remote libc makes results meaningless.
  • CET, seccomp, stack layout differences, or register clobbers often kill the magical one-shot path.

Resources

No bundled scripts/, references/, or assets/. Use the upstream gem README for installation, constraint-depth controls, and supported libc assumptions.

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

  1. MediumLicense · No license found

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, 202621cd5684438c90eSigned–

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