On March 2022, Bacon Protocol was exploited in a reentrancy, resulting in approximately $1 in losses. That makes the Bacon Protocol exploit the 474th largest DeFi incident out of 690 documented in our archive.
Attack Mechanics: How the Bacon Protocol Reentrancy Played Out
Exploit Class Applied to Bacon Protocol
The Bacon Protocol incident on March 5, 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, Bacon Protocol is 1 of 51 documented reentrancy incidents.
Bacon Protocol in Context
At $1, the Bacon Protocol exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — Curve (2023) at $41M.
Prior Reentrancy Before Bacon Protocol
The nearest reentrancy incident before Bacon Protocol was Visor Finance, 74 days earlier on December 21, 2021 ($8 lost). The same exploit class surfaced again within the reentrancy attack surface.
Impact & Recovery for Bacon Protocol
Bacon Protocol Loss Figure
The Bacon Protocol exploit caused $1 in losses — a minor (<$1M) incident and the 67th largest of 129 documented in 2022.
Where Bacon Protocol Sits Among Reentrancy Attacks
Ranked by loss size, Bacon Protocol is the 31st largest of 51 reentrancy incidents documented. That puts the Bacon Protocol loss below the class average of $2.87M.
Timeline Since the Bacon Protocol Incident
The Bacon Protocol exploit occurred 4.1 years ago (1,501 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for Bacon Protocol
Public post-mortem / on-chain analysis for the Bacon Protocol incident: view source.
FAQ
How much did Bacon Protocol lose?
The Bacon Protocol exploit in March 2022 resulted in $1 in losses — the 67th largest of 129 DeFi incidents that year.
When did the Bacon Protocol hack happen?
The Bacon Protocol exploit was recorded on March 5, 2022 — 1,501 days ago.
What type of exploit hit Bacon Protocol?
The Bacon Protocol 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 Bacon Protocol?
Our archive contains 51 documented reentrancy incidents. The Bacon Protocol incident is one of them.
How does Bacon Protocol compare to the largest Reentrancy attack?
The largest reentrancy incident in our archive is Curve (2023) at $41M. The Bacon Protocol loss is $1.
What are the three pillars of sustainability considered in the study?
Environmental, Social, and Corporate Governance (ESG).
What was a key finding regarding older cryptocurrencies?
Older cryptocurrencies' long-term volatility is sensitive to structural breaks in exogenous variables.