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/boofuzzWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package05a37232…d036dfcd
05a37232d6c5…fdecd036dfcd1 file · 1.4 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/fuzzing/boofuzz@21cd568
On this page
Protocol fuzzer framework with request modeling, session graphs, monitors, and structured logging.
Quick Start
pip install boofuzzfrom 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()Operator Flow (Recommended)
- Define protocol requests as
Request+Block+ primitives. - Build realistic session graph via
session.connect(...). - Add monitors (process/network/callback) before scaling testcases.
- Enable logs and reproduce individual failing testcases from run DB.
- 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_callbacksfor protocol-aware checks instead of only crash/no-crash signals. - Use
ProtocolSessionReferencewhen 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
FuzzLoggermultiplexer 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
- SKILL.md2.5 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 05a37232 | Signed | – |
More from AeonDave
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login