Smart contract exploits and ZK circuit bugs that AuditHub caught before launch

For engineers who want evidence, not promises: the bugs AuditHub found, how each one was caught, and what past DeFi hacks teach about stopping smart contract hacks.

35 issues caught in RISC Zero’s zkVM during development.

Every bug shown with the tool that produced the evidence.

Findings overview for the demo project shielded-pool: six findings from Vanguard, OrCa, ZK Vanguard and Picus in one table, the four AuditHub checks on a pull request, and the Picus Unsafe result with two witnesses.

Bugs caught before they became smart contract exploits

Each card shows the bug, the protocol it was found in, and the security tool that produced the evidence.

// 001

Underconstrained zkVM circuits

Protocol
RISC Zero zkVM
Tool
Picus

Picus verified determinism in CI as the zkVM evolved. 35 issues were found and mitigated during development.

Read the case study RISC Zero zkVM
// 002

Critical underconstrained bugs in the DivRem circuit

Protocol
Succinct SP1-Hypercube
Tool
Picus

Picus caught 3 critical underconstrained bugs before external audits, then verified every RISC-V chip deterministic. Running Picus on its own through AuditHub, Succinct later caught another critical issue on a new chip.

Read the case study Succinct SP1-Hypercube
// 003

Critical soundness bugs ahead of a prover upgrade

Protocol
Matter Labs ZKsync Airbender
Tool
Picus

Ahead of the V2 prover upgrade, Picus proved 21 of 26 circuits deterministic. 3 critical soundness bugs were fixed: one found by Picus, two by manual review of the verifier.

Read the case study Matter Labs ZKsync Airbender

How each bug was caught: the agent finds, the tool proves

Scout flags a suspicious path in your code. The matching security tool checks it and returns evidence you can reproduce, so a finding becomes a fact, not an opinion.

Scout AI - Findings

HighNeeds Review

Line 10

Signal r may be underconstrained

divide.circom:10
agent-findingcircuits/divide.circom

Picus - Evidence

Unsafe

Circuit is nondeterministic

Two distinct witnesses satisfy the constraints.

Witness 1, q2
Witness 2, q1

// COUNTEREXAMPLE FOUND

View both witnesses

Static analysis

Detects cross-contract bugs and returns the call graph and value flow.

Specification guided fuzzing

Tests your contracts against your [V] specs and returns exact inputs and traces.

Static analysis for ZK circuits

Catches likely underconstrained signals in your circuits.

Formal verification for ZK circuits

Proves your circuits are deterministic, or returns a concrete counterexample.

What past smart contract hacks teach about stopping the next one

Our pre-mortems walk through major DeFi exploits and the checks that would have flagged each one before launch.

Cross-contract reentrancy

Vanguard detects it

Broken protocol invariants

OrCa tests them

Underconstrained circuits

ZK Vanguard catches them, Picus proves their absence

Smart contract security case studies

How zkVM and L2 teams found bugs before their users did, and which tool proved each one.

zkVM

issues caught during development
35

RISC Zero runs Picus in CI on its zkVM

Underconstrained circuits were 6 of the 41 findings in the related security audit, and every critical one.

Catch your bugs before launch, not after an exploit

Find the next bug before launch: AI agents review your code, and security tools bring the evidence.