aeondave/oss-fuzz
offensive-tools/fuzzing/oss-fuzz/SKILL.md
Google-hosted continuous fuzzing service for open-source projects. Use for long-running, scalable fuzz campaigns, sanitizer-backed triage, and continuous bug reporting with reproducible local workflows.
$ install --global
skillsauthnpx skillsauth add aeondave/malskill oss-fuzzInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 4:45 AM202.5s1 file scanned
SKILL.md
- name:
- oss-fuzz
- description:
- Google-hosted continuous fuzzing service for open-source projects. Use for long-running, scalable fuzz campaigns, sanitizer-backed triage, and continuous bug reporting with reproducible local workflows.
- license:
- Apache-2.0
- compatibility:
- Service model for eligible OSS projects; local workflows via oss-fuzz repo + ClusterFuzz variants.
- author:
- GitHub Copilot
- version:
- 1.1
oss-fuzz
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
- https://google.github.io/oss-fuzz/
- https://github.com/google/oss-fuzz
- https://google.github.io/oss-fuzz/getting-started/new-project-guide/
- https://google.github.io/oss-fuzz/advanced-topics/reproducing/
- https://google.github.io/clusterfuzzlite/
Related Skills
aeondave/offensive-linux-role
data-ai
VerifiedTrustedCommunity
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
4SKILL.mdUpdated Jun 5, 2026
aeondave/ics-technique
development
VerifiedTrustedCommunity
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
4SKILL.mdUpdated Jun 2, 2026
aeondave/game-technique
tools
VerifiedTrustedCommunity
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
4SKILL.mdUpdated Jun 2, 2026
aeondave/hardware-technique
development
VerifiedTrustedCommunity
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.
4SKILL.mdUpdated Jun 2, 2026