offensive-fuzzing

Identify vulnerabilities in targets through structured fuzzing workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/RideMatch1/a.e.g.i.s --skill offensive-fuzzing-ridematch1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: offensive-fuzzing
Source: https://github.com/RideMatch1/a.e.g.i.s/tree/main/packages/skills/skills/offensive/snailsploit-fork/fuzzing
Command: npx skills add https://github.com/RideMatch1/a.e.g.i.s --skill offensive-fuzzing-ridematch1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlined approach to discovering security weaknesses in software by conducting structured fuzz campaigns across multiple targets and surfaces.

Core Features & Use Cases

  • End-to-end fuzzing workflow from target identification to crash triage.
  • Harness creation and corpus management for multiple fuzzers (AFL++, libFuzzer, Honggfuzz, Boofuzz, syzkaller).
  • Real-world use cases include testing file parsers, network protocols, kernel drivers, and embedded firmware.

Quick Start

Run a minimal fuzzing setup by selecting a target, choosing a fuzzer, and executing the harness against a small seed corpus to begin crash triage.

Frequently Asked Questions about offensive-fuzzing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a fuzzing harness for file parsers and network protocols?

Fuzzing harness creation for file parsers and network protocols requires selecting a fuzzer like AFL++ or libFuzzer and writing target-specific input handlers. This Skill provides structured guidance for building harnesses, curating seed corpora, and executing mutation strategies to identify vulnerabilities across multiple attack surfaces.

What is crash triage and how does it fit into the fuzzing workflow?

Crash triage is the end-stage process of analyzing fuzzer-generated crashes to determine exploitability and root cause. This Skill guides the complete triage workflow, helping you deduplicate crashes, identify unique vulnerabilities, and transition from raw crash artifacts to actionable security findings.

Can I use this to fuzz kernel drivers and embedded firmware?

Yes, fuzzing kernel drivers and embedded firmware is fully supported alongside file parsers and network protocols. The Skill guides harness creation and corpus management for complex targets, applying fuzzers like syzkaller for kernel surfaces and Honggfuzz for embedded environments.

Which fuzzing tools are supported for structured security testing?

Supported fuzzers include AFL++, libFuzzer, Honggfuzz, Boofuzz, and syzkaller. The Skill helps you select the appropriate fuzzer type based on your target surface, whether you are testing network protocols with Boofuzz or kernel drivers with syzkaller.

How do I start a minimal fuzzing setup to test a new target?

To start a minimal fuzzing setup, select your target, choose a compatible fuzzer, and execute the compiled harness against a small seed corpus. This Skill structures the quick start workflow from initial target identification through to initial crash triage.

What is the best way to fuzz EDR engines and language runtimes?

Fuzzing EDR engines and language runtimes demands specialized harness creation and targeted mutation strategies to discover deep vulnerabilities. This Skill provides an offensive security approach to structured fuzz campaigns, guiding corpus curation and fuzzer selection for these complex targets.