aeondave/aflplusplus
offensive-tools/fuzzing/aflplusplus/SKILL.md
Coverage-guided fuzzing framework for source and binary targets. Use when fuzzing C/C++ projects, parsers, CLI tools, or emulated binaries with high throughput, sanitizer-driven triage, and mature campaign orchestration.
$ install --global
skillsauthnpx skillsauth add aeondave/malskill aflplusplusInstall 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:44 AM206.0s1 file scanned
SKILL.md
- name:
- aflplusplus
- description:
- Coverage-guided fuzzing framework for source and binary targets. Use when fuzzing C/C++ projects, parsers, CLI tools, or emulated binaries with high throughput, sanitizer-driven triage, and mature campaign orchestration.
- license:
- Apache-2.0
- compatibility:
- Linux, macOS, Windows (WSL/Cygwin paths vary). Install from source, package manager, or Docker aflplusplus/aflplusplus.
- author:
- GitHub Copilot
- version:
- 1.1
aflplusplus
AFL++ is a modern AFL fork with stronger instrumentation, mutation strategies, and binary-only options.
Quick Start
# Build target with AFL++ wrappers
CC=afl-cc CXX=afl-c++ ./configure --disable-shared --disable-werror
make -j"$(nproc)"
# Fuzz stdin target
afl-fuzz -i seeds -o out -- ./target_bin
# Fuzz file-based target
afl-fuzz -i seeds -o out -- ./target_bin @@
Operator Flow (Recommended)
- Compile with
afl-clang-lto(orafl-clang-fastfallback). - Create a small valid seed set, then deduplicate (
afl-cmin). - Start one main instance and multiple secondary instances on the same
-odir. - Add one sanitizer build and one cmp-guided setup (
CMPLOG/Redqueen) in parallel. - Triage crashes with
afl-tmin, replay under sanitizer, and bucket by stack/PC.
Core Flags & Environment
| Flag | Description |
|------|-------------|
| -i <dir> | Seed corpus directory |
| -o <dir> | Output campaign directory |
| -x <dict> | Dictionary for structured tokens |
| -m <mb> | Memory limit |
| -t <ms> | Per-exec timeout |
| -M / -S | Parallel main/secondary instances |
| -d | Skip deterministic stage (faster starts) |
Useful env variables in real campaigns:
AFL_USE_ASAN=1/AFL_USE_UBSAN=1for sanitizer build variants.AFL_LLVM_CMPLOG=1for compare tracing binary used with-c.AFL_LLVM_LAF_ALL=1for compare splitting (when needed).AFL_IMPORT_FIRST=1to sync-import queue items early.AFL_TMPDIR=/dev/shm/...to reduce disk I/O pressure.
Practical Campaign Pattern
# 1) Corpus cleanup
afl-cmin -i seeds -o seeds_min -- ./parser @@
# 2) Main instance
afl-fuzz -M main -i seeds_min -o out -- ./parser @@
# 3) Secondary instances (example)
afl-fuzz -S fast -i seeds_min -o out -p fast -- ./parser @@
afl-fuzz -S explore -i seeds_min -o out -p explore -- ./parser @@
# 4) Resume campaign later
afl-fuzz -i - -o out -- ./parser @@
# 5) Minimize crash for triage
afl-tmin -i out/default/crashes/id:000000* -o crash.min -- ./parser @@
Tricks That Matter
- Prefer persistent-mode harnesses whenever possible; throughput jump is often decisive.
- For checksum-heavy formats, use fuzz-build conditionals (
FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION) to bypass blockers in harness builds. - For short CI fuzz windows, use faster calibration settings and reuse prior corpus.
- For dlopen-heavy targets, preload instrumented libs so map coverage is visible from startup.
Common Pitfalls
- Fuzzing network services over live sockets without harnessing: huge speed loss and weak reproducibility.
- Running all instances with identical profile/options: less strategy diversity.
- Skipping memory/time limits (
-m,-t) on unstable targets: noisy campaigns. - Treating corpus size as success metric; coverage and unique bug quality matter more.
Binary / Service Notes
- Binary-only: use AFL++ binary-focused docs (QEMU/Frida/Unicorn workflows) and keep strict replay discipline.
- Services/daemons: adapt to file/stdin/shared-memory harnessing for realistic throughput.
- GUI applications: isolate parser logic into fuzzable non-UI entrypoints.
Resources
- https://aflplus.plus/
- https://github.com/AFLplusplus/AFLplusplus
- https://aflplus.plus/docs/fuzzing_in_depth/
- https://aflplus.plus/docs/best_practices/
- https://google.github.io/oss-fuzz/
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