lcamtuf-afl-documentation
Points to Michał Zalewski’s (lcamtuf) canonical American Fuzzy Lop (AFL) documentation at lcamtuf.coredump.cx/afl-coverage-guided fuzzing concepts, afl-fuzz usage, and historical technical notes for C/C++ targets. Use when the user cites AFL classic, lcamtuf’s AFL page, or needs the original upstream reference-not as a substitute for current AFL++ docs or authorized fuzzing policy.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- lcamtuf-afl-documentation
- description
- Points to Michał Zalewski’s (lcamtuf) canonical American Fuzzy Lop (AFL) documentation at lcamtuf.coredump.cx/afl-coverage-guided fuzzing concepts, afl-fuzz usage, and historical technical notes for C/C++ targets. Use when the user cites AFL classic, lcamtuf’s AFL page, or needs the original upstream reference-not as a substitute for current AFL++ docs or authorized fuzzing policy.
03 SKILL.md 正文
lcamtuf - American Fuzzy Lop (AFL) documentation (reference)
Educational routing only. This skill does not mirror the full site. Open the live pages for complete instructions, file lists, and any upstream notes.
Canonical URL
- American Fuzzy Lop (AFL) - hosted on lcamtuf.coredump.cx (Michał Zalewski’s site).
What it is
AFL is a coverage-guided fuzzer aimed primarily at C/C++ binaries via compile-time instrumentation (e.g. afl-gcc / afl-clang / LLVM modes) and the afl-fuzz driver. The published material on this site includes the original project narrative, quick-start style guidance, status screen semantics, and performance / tuning notes that many tutorials still cite.
Typical mental model for readers:
| Topic | Role |
|---|---|
| Instrumentation | Rebuild the target with AFL’s compilers/wrappers so edges are tracked. |
| Corpus & seeds | Start from small valid inputs; AFL mutates and discovers new paths. |
| Fuzzing loop | afl-fuzz runs; UI shows paths, crashes, hangs, stability-interpret per upstream docs. |
| Crashes | Triaged as potential bugs; verify, minimize, report responsibly. |
Modern fork (operational note)
Active development of the AFL lineage for many teams is AFL++ (feature-rich fork, maintained tooling). Use this skill when the user explicitly wants lcamtuf’s classic page or historical AFL terminology; use AFL++ docs for current flags, compilers, and CI integration on new projects.
How to combine with blockint
| Need | Skill |
|---|---|
| Solidity / EVM smart contract review | evm-solidity-defi-triage-agent, defi-security-audit-agent |
| Solana / Rust program security | solana-defi-vulnerability-analyst-agent, sealevel-attacks-solana |
| C/C++ native code in security research | lcamtuf-afl-documentation (AFL concepts) + project-specific build docs |
Guardrails
- Scope - Fuzz only systems you own or are explicitly authorized to test; follow program rules and laws.
- Triaging - Not every crash is exploitable; confirm with debugging and vendor disclosure practice.
- Stale tooling - Compare classic AFL behavior with current compiler and AFL++ release notes before production pipelines.
Goal: a stable pointer to lcamtuf.coredump.cx/afl for classic AFL documentation and terminology in security / fuzzing conversations.
04 同仓库更多 Skills
bastion
Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.
web2-api-firewall-administrator
Guides configuring Bastion Web2 API adapter policies for the Trust Runtime. Covers endpoint allowlists, provider budgets, rate limits, content inspection (PII/secrets detection), header filters, and OpenAPI spec-based auto-configuration. Use when configuring API call security for AI agents, setting provider spending caps, inspecting outbound API traffic, or setting up the Web2 adapter.
transaction-screening-workflow-concepts
Educational map of transaction-centric compliance screening-transfer as the atomic unit, deposit vs withdrawal direction, single and CSV import, transaction list and detail views, per-transfer screening, rescreen, and STR-style exports. Use when the user asks how monitoring UIs treat tx hashes, directions, or regulatory reporting hooks-not for legal filing advice or evading reporting.
solana-tracing-specialist
Guides Solana-specific on-chain forensics-ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX/Jito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.
solana-onchain-intelligence-resources
Companion to blockint-skills Solana work-official doc indexes and stacks for RPC/indexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy/regulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev/testing), coral-xyz sealevel-attacks (security pattern examples), Neodyme Solana Security Workshop (workshop.neodyme.io), and Osec Solana auditor introduction blog (osec.io). Use when the user needs pointers to Helius, Range AI, Tavily, PayAI x402, React Flow, Solana.com skills, or SPI alongside on-chain forensics-not as a substitute for reading current provider docs, legal counsel, or API keys.
solana-defi-vulnerability-analyst-agent
Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor/native programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad/bonding-curve issues, or evidence-backed severity findings without exploits or private keys.