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

oss-fuzz

⁨Auth/lab ref: Google-hosted continuous fuzzing service for open-source projects. For long-running, scalable fuzz campaigns, sanitizer-backed triage, and continuous bug reporting with reproducible local workflows.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsApache-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/oss-fuzz

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

SignatureSigned, ed25519
OqUWm9mhng…siyOGECw==The CLI checks the SHA-256 and the signature before it writes a file.
Package3a459503…023cfdae
3a45950335b2…865c023cfdae1 file · ⁦1.4 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/fuzzing/oss-fuzz@21cd568

Continuous fuzzing platform that runs supported engines (libFuzzer, AFL++, Honggfuzz, Centipede) at scale.

When to Use

  • You maintain an open-source project and need persistent fuzz coverage.
  • You want automated sanitizer-based crash reporting and regression tracking.
  • You need multi-language support beyond ad-hoc local campaigns.

Core Flow

  1. Add project integration config to OSS-Fuzz repo.
  2. Define build/fuzz targets and seed corpora.
  3. Validate locally with OSS-Fuzz tooling.
  4. Submit and monitor issue stream.

Local Validation Flow

bash
python3 infra/helper.py build_image <project>
python3 infra/helper.py build_fuzzers --sanitizer address <project>
python3 infra/helper.py check_build <project>
python3 infra/helper.py run_fuzzer --corpus-dir=<tmp-corpus> <project> <fuzz_target>

Run additional sanitizer/engine combinations when integration quality is uncertain.

Reproduction Flow (Bug Fix Loop)

bash
python3 infra/helper.py reproduce <project> <fuzz_target> <testcase_path>

If the bug is not reproducible immediately:

  • pull latest images,
  • match sanitizer and architecture from report,
  • retry with exact target binary and runtime flags.

Practical Tricks

  • Keep seed corpus and dictionaries small but meaningful; large noisy corpora can slow signal.
  • Prefer statically linked fuzz binaries in build scripts for runtime compatibility.
  • Use Fuzz Introspector reports to detect low-reach fuzz targets and prioritize harness work.

Common Pitfalls

  • Skipping local check_build before PR submission.
  • Treating one sanitizer pass as complete validation.
  • Ignoring architecture-specific issues (some findings reproduce only on i386 or x86_64).

Notes

  • Best for continuous defect discovery, not one-off local triage.
  • For closed-source/internal projects, use ClusterFuzz/ClusterFuzzLite style alternatives.
  • Build artifacts copied to $OUT should remain reasonably small to avoid slow transfer/unzip cycles.

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

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