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

boofuzz

⁨Auth/lab ref: Python network protocol fuzzing framework (Sulley successor). For stateful TCP/UDP protocol fuzzing, request-graph modeling, monitor-driven crash detection, and reproducible protocol campaign workflows.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsGPL-2.0synced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

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

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

SignatureSigned, ed25519
gHFeKXL3rt…8z52rHCw==The CLI checks the SHA-256 and the signature before it writes a file.
Package05a37232…d036dfcd
05a37232d6c5…fdecd036dfcd1 file · ⁦1.4 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/fuzzing/boofuzz@21cd568

Protocol fuzzer framework with request modeling, session graphs, monitors, and structured logging.

Quick Start

bash
pip install boofuzz
python
from boofuzz import Session, Target, TCPSocketConnection, s_initialize, s_string, s_get

s_initialize("req")
s_string("HELLO", fuzzable=True)

session = Session(target=Target(connection=TCPSocketConnection("127.0.0.1", 9999)))
session.connect(s_get("req"))
session.fuzz()
  1. Define protocol requests as Request + Block + primitives.
  2. Build realistic session graph via session.connect(...).
  3. Add monitors (process/network/callback) before scaling testcases.
  4. Enable logs and reproduce individual failing testcases from run DB.
  5. Iterate on protocol model quality (field sizes, delimiters, checksums, dependencies).

Best Use Cases

  • Custom/legacy network protocols.
  • Stateful handshake + multi-step message flows.
  • Harnesses requiring explicit restart/monitor logic.

Practical Tricks

  • Use post_test_case_callbacks for protocol-aware checks instead of only crash/no-crash signals.
  • Use ProtocolSessionReference when later messages need dynamic data extracted from prior responses.
  • Keep a strict separation between:
    • transport connection behavior,
    • protocol message modeling,
    • health/monitoring logic.
  • Prefer deterministic target reset routines in monitor hooks.

Common Pitfalls

  • Blind mutation of raw bytes without block/field modeling wastes boofuzz strengths.
  • No monitor/restart chain -> flaky crash attribution.
  • Overly broad callback side effects -> non-deterministic failures.

Logging & Triage

  • Use text/CSV/curses loggers via FuzzLogger multiplexer for both operator visibility and artifacts.
  • Persist each run DB (boofuzz-results/run-*.db) and reopen for post-campaign review.
  • Keep concise crash synopsis in monitor implementations (get_crash_synopsis).

Resources

Files in this version

Permissions

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

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

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

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