offensive-tools/fuzzing/honggfuzz/SKILL.md
Feedback-driven, high-speed fuzzer with multi-process/thread execution and persistent fuzzing. Use for local binary fuzzing, instrumentation-guided campaigns, sanitizer-assisted triage, and corpus minimization workflows.
npx skillsauth add aeondave/malskill honggfuzzInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
General-purpose evolutionary fuzzer with software/hardware coverage options and strong persistent-mode performance.
# Compile with wrappers
./hfuzz_cc/hfuzz-clang -o target target.c
# Run with file placeholder
./honggfuzz -i seeds -- ./target ___FILE___
# Persistent mode
./honggfuzz -P -i seeds -- ./target
___FILE___ or -s stdin mode).-P) as soon as target design allows.-M) periodically.| Flag | Description |
|------|-------------|
| -i <dir> | Input corpus directory |
| --output <dir> | Output directory for dynamic/minimized corpus |
| -P | Persistent mode |
| -n <threads> | Number of fuzzing threads |
| -M | Corpus minimization mode |
| -x | Disable instrumentation feedback (static mode) |
| -s | Feed input via stdin |
| --sanitizers | Enable sanitizer-aware handling (build-dependent) |
-dict for highly structured input grammars.-t) and mutation count per run (-r) before scaling threads.--rlimit_*) to prevent campaign collapse.-x) baseline vs coverage-driven modes to validate benefit.data-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
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).
tools
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).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.