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-fuzzWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package3a459503…023cfdae
3a45950335b2…865c023cfdae1 file · 1.4 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/fuzzing/oss-fuzz@21cd568
On this page
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
- Add project integration config to OSS-Fuzz repo.
- Define build/fuzz targets and seed corpora.
- Validate locally with OSS-Fuzz tooling.
- Submit and monitor issue stream.
Local Validation Flow
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)
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_buildbefore PR submission. - Treating one sanitizer pass as complete validation.
- Ignoring architecture-specific issues (some findings reproduce only on
i386orx86_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
$OUTshould remain reasonably small to avoid slow transfer/unzip cycles.
Resources
Files in this version
- SKILL.md2.6 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 | 3a459503 | 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