Revest Hack

TOTAL LOST $2.0M
Medium Other

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #647 By amount stolen
Protocol Type Exploit/Other Target category

Incident Overview

An example of the transaction:

https://etherscan.io/tx/0x613b2de3…a5d9f5

The exploiter's address:

https://etherscan.io/address/0xef967ece…5bd58b

The attacker minted a massive amount of FNFT with no cost and used the minted FNFT to drain assets in the vault.

The attacker:

- flashloaned 2 ECO tokens from Uniswap

- called "mintAddressLock" in the Revest contract twice to get 2 FNFT[ID 1036] tokens and 7,700,00 FNFT[ID 1037] tokens

- during the second FNFT minting process, the attacker exploited the reentrancy issue and called the function “depositAdditionalToFNFT” to cause the minted FNFT can be used to drain assets in the vault

- called "withdrawFNFT" to drain assets from the vault by burning 7,700,001 FNFT[ID 1037] tokens and repaying the flashloan.

Stolen funds were deposited into the Tornado Cash mixer:

https://bloxy.info/txs/transfers_from/0xef967ece…5bd58b?currency_id=1

Incident Report

Protocol / Project Revest
Date of Incident
Attack Technique Other
Classification NFT

Protocol Information

Protocol Type Exploit/Other
Official Website revest.finance/
Protocol Twitter/X @RevestFinance
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Medium of Exchange DeFi Payments Smart Contracts Ethereum Ecosystem Polygon Ecosystem Binance Ecosystem Binance Listing

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Revest's contract logic - root cause: nft
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Other audit checklist and test coverage

If you're auditing a protocol with similar architecture to Revest, these are the critical security checks that could have prevented this incident (March 2022).

  • Verify all logic paths related to Other are guarded by proper access controls and input validation
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Sources & References

Learn to Prevent the Next Revest

The Revest hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial