On March 2022, Revest Finance was exploited in a reentrancy, resulting in approximately $11 in losses. That makes the Revest Finance exploit the 462nd largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Revest Finance Reentrancy Played Out
Exploit Class Applied to Revest Finance
The Revest Finance incident on March 27, 2022 is classified as a Reentrancy. A malicious contract re-enters a vulnerable function before state is updated, letting it drain funds multiple times. In the full archive, Revest Finance is 1 of 51 documented reentrancy incidents.
Revest Finance in Context
At $11, the Revest Finance exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — Curve (2023) at $41M.
Prior Reentrancy Before Revest Finance
The nearest reentrancy incident before Revest Finance was Agave Finance, 12 days earlier on March 15, 2022 ($1 lost). The same exploit class surfaced again within the reentrancy attack surface.
Impact & Recovery for Revest Finance
Revest Finance Loss Figure
The Revest Finance exploit caused $11 in losses — a minor (<$1M) incident and the 61st largest of 129 documented in 2022.
Where Revest Finance Sits Among Reentrancy Attacks
Ranked by loss size, Revest Finance is the 29th largest of 51 reentrancy incidents documented. That puts the Revest Finance loss below the class average of $2.87M.
Timeline Since the Revest Finance Incident
The Revest Finance exploit occurred 4.1 years ago (1,479 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Revest Finance
Public post-mortem / on-chain analysis for the Revest Finance incident: view source.
FAQ
How much did Revest Finance lose?
The Revest Finance exploit in March 2022 resulted in $11 in losses — the 61st largest of 129 DeFi incidents that year.
When did the Revest Finance hack happen?
The Revest Finance exploit was recorded on March 27, 2022 — 1,479 days ago.
What type of exploit hit Revest Finance?
The Revest Finance incident is classified as a Reentrancy. A malicious contract re-enters a vulnerable function before state is updated, letting it drain funds multiple times.
How common is the Reentrancy pattern seen at Revest Finance?
Our archive contains 51 documented reentrancy incidents. The Revest Finance incident is one of them.
How does Revest Finance compare to the largest Reentrancy attack?
The largest reentrancy incident in our archive is Curve (2023) at $41M. The Revest Finance loss is $11.
How are the models ranked in the study?
Using Kendall W test of concordance.
How does the hybrid GA-LSTM model's performance compare to benchmark models?
The GA-optimized LSTM model outperforms the benchmark model in all error measures tested.