Exploit verification

Some workspaces have access to exploit verification — a feature that goes beyond static analysis and tries to show whether a vulnerability is exploitable in practice.

Concept

When enabled, Guardix runs a separate pipeline that:

1. Prepares an isolated execution environment (sandbox) aligned with your contract’s chain context.
2. Attempts exploit scenarios against the snapshot.
3. Surfaces outcomes — for example, whether the issue was reproducible and what happened during the attempt.

What you see

• Progress for exploit-related jobs
• Logs (often redacted) for transparency without exposing secrets
• Status of each attempt so you are not left with ambiguous empty states

Availability may be feature-gated and require a completed audit as a prerequisite.

Starting exploit runs

Exploit verification is launched from a completed code audit:

1. Open the repository from Code Audits.
2. Select the completed scan you want to test.
3. Open the Exploits tab and start a run from there.

There is no separate top-level “start exploit” flow — exploits are always tied to audit findings from a finished scan.

Framing

Exploit verification is a strong signal, not a guarantee. A failed attempt does not always mean “safe,” and a succeeded attempt does not replace a full manual audit for your business context.