ZK circuit static analysis, from private input leakage to underconstrained signals

ZK Vanguard runs in your CI, groups related findings, and supports custom detectors.

For Circom, Halo2, Zirgen and Plonky3.

Results in seconds to minutes, depending on complexity.

divide.circom open in AuditHub with line 10 flagged by ZK Vanguard: the Tool Findings grouped by severity, the likely underconstrained signal r handed to Picus, and the ZK Vanguard check on the pull request.

What ZK Vanguard detects in your ZK circuits

Each detector targets one vulnerability class and looks at both sides of your circuit: the code that computes the witness and the constraints that check it.

// 001

Underconstrained signals

Signals without enough constraints, which let an attacker craft proofs with arbitrary values.

// 002

Private input leakage

Private witness data exposed through the structure of the circuit.

// 003

Non-deterministic dataflow

Outputs that depend on values that should not influence them.

// 004

Compute-constrain mismatch

Values the witness computes that the constraints never enforce.

// 005

Unused subcomponents

Components that exist but are not connected to the constraint system.

// 006

Unsafe witness generation

Divide by zero and control flow that depends on signal values.

Plus checks for out-of-range signals and unused fields, and custom detectors for your own patterns.

How ZK circuit static analysis works in ZK Vanguard

ZK Vanguard reads your circuit without running it. Its detectors compare witness generation with the constraints, and catch the places where the two disagree.

// 001

Connect your repository

Circom, Halo2, Zirgen or Plonky3 circuits.

// 002

Run the analysis

Pick your detectors, ZK Vanguard checks witness generation and constraints.

// 003

Review grouped findings

Related findings are grouped, and marking a root cause clears linked false alarms in bulk.

From AI finding to ZK static analysis evidence

Scout flags a circuit it suspects of leaking a private input. ZK Vanguard checks it and returns the evidence: the signals involved and the exact lines in your circuit.

Scout AI - Findings

HighNeeds Review

Line 18

Private input may leak through a public output

withdraw.circom:18
agent-findingcircuits/withdraw.circom

ZK Vanguard - Evidence

Evidence found

Private input leakage detected

The signals involved and the exact lines in your circuit.

Signals involved2signals
Exact lines12, 18

// PRIVATE INPUT LEAKAGE

View signals and lines

Custom detectors for your circuit's own risks

Write detectors for the patterns specific to your circuits and your ZK framework. They run on the same engine as the built-in ones and land in the same findings table.

// custom detector
// pattern: specific to your circuits
// framework: your ZK framework
// engine: same as the built-in detectors
// output: the same findings table
Pull request with the AuditHub ZK Vanguard check: completed, needs review.

ZK circuit static analysis in GitHub Actions, on every commit

ZK Vanguard runs in your CI and reports in seconds to minutes, depending on complexity. Every change to your circuits gets a fast first pass during development, not after the fact.

ZK Vanguard catches, Picus proves

ZK Vanguard catches likely underconstrained signals; Picus proves their absence. Run ZK Vanguard first for a fast pass, then Picus for a guarantee that holds for every input.

Static analysis for ZK circuits

Catches likely underconstrained signals in a fast first pass.

Formal verification for ZK circuits

Proves the absence of underconstrained signals, for every input.

Static analysis alongside your ZK security audit

ZK Vanguard checks your circuits on every change, so your auditors start on cleaner circuits and spend their time on design and logic. The audit still gives you a signed expert review.

Before audit

During audit

After audit

ZK Vanguard // EVERY CHANGE
ZK Vanguard task summary on the demo project: steps, findings and artifacts.
AuditHub ZK Vanguard check on a pull request: completed, needs review.
ZK Vanguard recent tasks across versions v1 to v3 of the demo project.

ZK circuit static analysis FAQ

What is ZK circuit static analysis?

It examines your circuit code without executing it to find vulnerabilities before deployment. ZK Vanguard looks at both witness generation and constraints, and catches where they disagree.

What is an underconstrained signal?

A signal without enough constraints to fix its value. An attacker can then craft a valid proof with an arbitrary value.

Which ZK languages does ZK Vanguard support?

Circom, Halo2, Zirgen and Plonky3.

How long does an analysis take?

Seconds to minutes, depending on the complexity of your circuits.

What is the difference between ZK Vanguard and Picus?

ZK Vanguard catches likely underconstrained signals; Picus proves their absence. They work together: ZK Vanguard runs first for speed, Picus follows with formal verification.

Still have questions? Contact us

Learn more about ZK circuit security

Catch underconstrained signals before your circuits ship

Run ZK Vanguard on your ZK circuits today.