web3-audit

Audits Solidity and Rust smart contracts for ten DeFi vulnerability classes with Foundry PoC templates.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/inventashif/helpful-code-sidekick --skill web3-audit-inventashif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web3-audit
Source: https://github.com/inventashif/helpful-code-sidekick/tree/main/scripts/hackerai/skills/bughunter/web3-audit
Command: npx skills add https://github.com/inventashif/helpful-code-sidekick --skill web3-audit-inventashif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Smart contract auditors and bug bounty hunters waste hours on low-value targets and miss recurring vulnerability patterns. This Skill provides a systematic audit methodology covering the ten DeFi bug classes that account for most paid Immunefi findings, plus pre-dive kill signals to decide whether a target is worth hunting before reading any code. ## Core Features & Use Cases - Ten Bug Class Playbooks: Covers accounting desynchronization, access control, incomplete code paths, off-by-one boundaries, oracle manipulation, ERC4626 vault attacks, reentrancy, flash loans, signature replay, and proxy issues, each with vulnerable code patterns and grep commands. - Target Scoring & Kill Signals: Evaluates TVL, audit history, codebase size, and bounty caps to filter out low-ROI targets before investing audit time. - Foundry PoC Template: Provides a ready exploit-test skeleton with cheatcodes (vm.prank, deal, fork) so findings meet Immunefi's mandatory proof-of-concept requirement. - Use Case: Given a newly deployed ERC4626 vault with $20M TVL and no top-tier audit, run the grep patterns for exchange-rate manipulation and sibling-function modifier checks, then confirm any finding with a single forge test invocation. ## Quick Start Audit this Solidity contract for the ten DeFi bug classes and write a Foundry proof of concept for any finding.

Frequently Asked Questions about web3-audit

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

FAQPage Schema
How do I audit a Solidity smart contract for vulnerabilities?

Start with pre-dive kill signals like TVL and prior audits, then grep for the ten bug classes: accounting desync, access control, incomplete paths, off-by-one, oracle issues, ERC4626 attacks, reentrancy, flash loans, signature replay, and proxy flaws. Confirm each finding with a Foundry test.

What are the most common DeFi smart contract bugs?

Accounting state desynchronization leads at roughly 28% of Critical Immunefi findings, followed by access control flaws at 19% and incomplete code paths at 17%. Oracle manipulation and reentrancy produce the largest individual payouts.

How do I write a Foundry proof of concept for Immunefi?

Use a forge test that forks mainnet with vm.createSelectFork, funds accounts via deal, executes the exploit under vm.startPrank, and asserts the economic impact with assertGt on balances. Immunefi auto-rejects submissions without a runnable PoC.

When is a bug bounty target not worth auditing?

Skip targets with TVL under $500K, two or more top-tier audits on a simple protocol, or a max realistic payout below $10K computed as min of 10% of TVL and the program cap. Large audited codebases over 500K lines rarely yield findings.

Does this audit approach work for Solana or Move contracts?

The methodology extends beyond Solidity: Solana audits use the Anchor framework with sealevel-attacks PoCs, and Move chains like Aptos and Sui use move-prover and aptos CLI testing. The bug-class reasoning and kill signals still apply.