Rust Security
Rust Smart Contract Security: Static Analysis and Common Bugs
Common bugs in Rust smart contracts and how static analysis catches them before deployment.
AI agents review your code, and OrCa fuzzes it against your specification.
Built by the Veridise auditors behind 150+ security audits.

Scout learns your protocol, hunts for exploitable bugs in your Rust contracts, tests each one with OrCa where a property applies, and remembers what it learned for the next run.
// 001
Models your contracts, entry points and who may call them.
// 002
Looks for missing checks, arithmetic errors and panics an attacker can trigger.
// 003
Runs OrCa against the property at stake.
// 004
Keeps what it learned for the next run.
OrCa is the security tool for your Rust contracts: specification guided fuzzing, built on formal methods.
OrCa tests your contracts against the behavior you specify in [V], or against the existing specification library. It generates thousands of test cases and returns exact inputs and traces for every violation.
// RUST
Explore OrCa →Also shipping Solidity? Vanguard adds static analysis on your Solidity contracts.
Well-known bug classes in Rust contracts. Scout reviews each one; OrCa tests the ones you can state as a property.
| Vulnerability | What happens | Covered by |
|---|---|---|
| Integer overflow and underflow | Release builds wrap silently unless overflow checks are enabled. | Scout, OrCa |
| Missing authorization checks | Entry points that never verify who is calling. | Scout, OrCa |
| Panics and unchecked unwraps | An unwrap or out-of-bounds index aborts the call and can block a critical path. | Scout, OrCa |
| Rounding errors | Integer division in fee and share math that leaks value over time. | Scout, OrCa |
| State changes around external calls | State read or written in the wrong order around a call to another contract. | Scout |
| Broken invariants | Accounting, supply or collateral rules that stop holding. | OrCa |
Scout flags a fee calculation that rounds in the user’s favor. OrCa tests the property you specified and returns the evidence: the exact call sequence and inputs that break it.
Scout AI - Findings
Line 75
First depositor can inflate the share price
OrCa - Evidence
Share price manipulation reproduced
The exact inputs and the trace that break the expected behavior.
// COUNTEREXAMPLE FOUND
Keep writing and building your contracts with cargo. Connect your GitHub repository and run checks in GitHub Actions on every commit, so findings arrive during development.
Writing Rust with a coding agent? AuditHub MCP runs OrCa from your session.
AuditHub checks your Rust code on every change, so your auditors start from a cleaner baseline and spend their time on design and logic. The audit still gives you a signed expert review.
Before audit
During audit
After audit



OrCa was shaped on real engagements by the Veridise auditors behind AuditHub.
An expert review of your contracts for flaws such as missing authorization checks, arithmetic errors and broken invariants before deployment. AuditHub keeps checking between audits: AI agents review the code and OrCa tests it against your specification.
Vanguard’s static analysis covers Solidity. On Rust, AI agents review your code and OrCa fuzzes it against your specification.
You can write your own in [V], or start from the existing specification library.
No. It checks every change between audits, and the audit gives you a signed expert review.
Still have questions? Contact us
Rust Security
Common bugs in Rust smart contracts and how static analysis catches them before deployment.
Security Tools
What static analysis, fuzzing and formal proofs each catch, and how they fit together in one workflow.
Smart Contract Security
The main risks in smart contracts, the controls that reduce them, and how to check that your code really holds.
Start fuzzing your Rust code with OrCa today.