OpenViSTAI · Agents · Blockchain · Crypto
Menu
Developer Tools

Ityfuzz

Ityfuzz is an open-source Rust command-line hybrid fuzzer for EVM and MoveVM smart contracts. It combines symbolic execution, fuzzing and chain forking to investigate contract behavior and generate exploit-oriented test cases.

Independent OpenViST project profile, based on linked sources.

Ityfuzz — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Ityfuzz when a security workflow needs bytecode-level fuzzing, symbolic execution, Foundry initialization or a fork of a deployed EVM contract at a chosen block. Its documented MoveVM support also makes it relevant to Aptos- and Sui-oriented contract development.

Who it is for

  • Smart-contract developers
  • Blockchain security researchers
  • Foundry users testing invariant contracts
  • Teams investigating deployed EVM contracts

Documented uses

  • Search smart contracts for security vulnerabilities through hybrid fuzzing
  • Test deployed contracts at selected chain states using chain forks
  • Invoke Foundry invariant tests through Ityfuzz
  • Explore reentrancy, flashloan and liquidation scenarios
  • Fuzz contracts without source code through decompilation
Before you choose

Requirements & limits

The repository is public and MIT-licensed. Ityfuzz is documented as a CLI for Linux, macOS and Windows. The primary workflows require a local contract or test setup; forked deployed-contract testing additionally uses an RPC endpoint and, in the documented example, an Etherscan API key.

  • It combines fuzzing with symbolic execution rather than relying on fuzzing alone.
  • Chain forking supports testing deployed contracts at a selected block in the documented workflow.
  • Decompilation allows fuzzing contracts without source code.
  • Foundry initialization and invariant-test invocation support existing Foundry workflows.
  • Flashloan and liquidation simulation target DeFi-oriented testing scenarios.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Run a Foundry invariant test through Ityfuzz

Use Ityfuzz to invoke a Foundry invariant test defined in test/Invariant.sol.

Before you start

  • Ityfuzz installed as a command-line tool
  • A Foundry project containing test/Invariant.sol and an Invariant contract
  • A documented Foundry test invocation to replace

Steps

  1. Identify the invariant contract and source path, such as test/Invariant.sol:Invariant.

  2. Pass that target to Ityfuzz with the documented evm mode and Foundry test invocation.

  3. Review the tool's output as the test run proceeds.

Expected outcome

Ityfuzz invokes the specified Foundry invariant test for hybrid fuzzing.

Guide limitations

  • The documented example does not provide resulting test output or establish a successful run.
  • The recipe covers invocation, not a complete CI integration.
Source-based practical guide

Set up a forked test of a deployed Polygon contract

Configure a documented fork-based fuzzing invocation for deployed contracts at a selected Polygon block.

Before you start

  • Ityfuzz installed
  • An EVM RPC endpoint
  • Target contract addresses
  • Polygon chain selection and an onchain block number
  • An Etherscan API key for the documented example

Steps

  1. Set ETH_RPC_URL to an RPC endpoint.

  2. Pass the target addresses to the evm command.

  3. Select Polygon and provide the onchain block number.

  4. Add the documented flashloan option and Etherscan API key where required by the example.

Expected outcome

Ityfuzz is configured to fuzz the selected deployed contracts against a Polygon fork at the specified block.

Guide limitations

  • The example does not establish support for every EVM chain or RPC provider.
  • The source documents the invocation, not the resulting findings.
  • The example's displayed API key should not be reused; obtain an appropriate key as directed by the project.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
2 October 2026
Original website title
fuzzland/ityfuzz · Official homepage title · retained in its source language