On March 2022, Agave Finance was exploited in a reentrancy, resulting in approximately $1 in losses. That makes the Agave Finance exploit the 474th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Agave Finance Reentrancy Played Out
Exploit Class Applied to Agave Finance
The Agave Finance incident on March 15, 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, Agave Finance is 1 of 51 documented reentrancy incidents.
Agave Finance in Context
At $1, the Agave Finance exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — Curve (2023) at $41M.
Prior Reentrancy Before Agave Finance
The nearest reentrancy incident before Agave Finance was Hundred Finance, 2 days earlier on March 13, 2022 ($1 lost). The same exploit class surfaced again within the reentrancy attack surface.
Agave Finance Vulnerability Signature
The primary source categorises the Agave Finance exploit specifically as “ERC667 Reentrancy”. This narrower label is entity-specific: it reflects how the Agave Finance contract failed, rather than the broad reentrancy pattern alone.
Impact & Recovery for Agave Finance
Agave Finance Loss Figure
The Agave Finance exploit caused $1 in losses — a minor (<$1M) incident and the 67th largest of 129 documented in 2022.
Where Agave Finance Sits Among Reentrancy Attacks
Ranked by loss size, Agave Finance is the 31st largest of 51 reentrancy incidents documented. That puts the Agave Finance loss below the class average of $2.87M.
Timeline Since the Agave Finance Incident
The Agave Finance exploit occurred 4.1 years ago (1,491 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Agave Finance
Public post-mortem / on-chain analysis for the Agave Finance incident: view source.
FAQ
How much did Agave Finance lose?
The Agave Finance exploit in March 2022 resulted in $1 in losses — the 67th largest of 129 DeFi incidents that year.
When did the Agave Finance hack happen?
The Agave Finance exploit was recorded on March 15, 2022 — 1,491 days ago.
What type of exploit hit Agave Finance?
The Agave 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 Agave Finance?
Our archive contains 51 documented reentrancy incidents. The Agave Finance incident is one of them.
How does Agave Finance compare to the largest Reentrancy attack?
The largest reentrancy incident in our archive is Curve (2023) at $41M. The Agave Finance loss is $1.
What future advancements are necessary for DAG-based platforms according to the document?
They need to evolve in feature set to reach the same level of programmability as blockchain platforms.
How is Bitcoin trading volume related to its volatility according to the study?
Increasing trading volume predicts lower Bitcoin volatility, suggesting higher levels of trust or confidence in Bitcoin.