web3-audit

Identify and prioritize DeFi smart-contract vulnerabilities across 10 bug classes.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/zer0xhamid/LogicHunter_v2 --skill web3-audit-zer0xhamid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web3-audit
Source: https://github.com/zer0xhamid/LogicHunter_v2/tree/main/skills/web3-audit
Command: npx skills add https://github.com/zer0xhamid/LogicHunter_v2 --skill web3-audit-zer0xhamid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditors and security engineers struggle to comprehensively identify and remediate vulnerabilities in DeFi smart contracts, given the complexity and volume of patterns across token, proxy, and oracle logic.

Core Features & Use Cases

  • 10 bug classes covering accounting desync, access control, incomplete path, off-by-one, oracle, ERC4626, reentrancy, flash loan, signature replay, and proxy issues
  • Pre-dive kill signals (e.g., TVL thresholds, audit recency) to quickly filter low-signal targets
  • Foundry PoC template and grep patterns to reproduce findings and validate mitigations
  • Real Immunefi paid examples to illustrate tangible impact and reward scales
  • Use Case: auditors can rapidly assess a new solidity project and produce actionable defense recommendations

Quick Start

Run a web3-audit assessment on a Solidity contract to identify high-priority DeFi bug classes

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 DeFi vulnerabilities?

To audit a Solidity smart contract for DeFi vulnerabilities, use this Skill to classify issues across 10 bug classes including reentrancy, oracle manipulation, and flash loan attacks. It provides Foundry PoC templates and grep patterns to reproduce findings and frame remediation steps.

What are the most common DeFi smart contract bug classes?

The most common DeFi smart contract bug classes include accounting desync, access control, incomplete path, off-by-one, oracle, ERC4626, reentrancy, flash loan, signature replay, and proxy issues. These 10 categories cover the primary vulnerability patterns in decentralized finance protocols.

How do I write a Foundry PoC for smart contract vulnerabilities?

To write a Foundry PoC for smart contract vulnerabilities, use the provided Foundry PoC templates to reproduce findings and validate mitigations. These templates integrate with grep patterns to classify issues and map attack surfaces during security audits.

Can I use web3-audit for Rust smart contracts?

Yes, you can use web3-audit for Rust smart contracts. The vulnerability identification and prioritization process applies to both Solidity and Rust contracts, guiding pre-dive analysis, pattern matching, and template-driven testing across DeFi protocols.

Does web3-audit require Foundry to run security assessments?

Yes, web3-audit requires Foundry-based workflows to reproduce findings and validate mitigations. The Skill provides grep patterns and PoC templates that depend on Foundry to classify issues and map attack surfaces during DeFi protocol audits.

How do I filter low-signal targets before a DeFi security audit?

To filter low-signal targets before a DeFi security audit, apply pre-dive kill signals such as TVL thresholds and audit recency checks. This quickly filters out low-value targets, allowing auditors to focus on high-priority contracts.