On May 2021, BurgerSwap suffered a reentrancy — the first of 51 documented reentrancy incidents in our archive where the loss figure was not publicly disclosed but the exploit pattern is documented below.
Attack Mechanics: How the BurgerSwap Reentrancy Played Out
Exploit Class Applied to BurgerSwap
The BurgerSwap incident on May 27, 2021 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, BurgerSwap is 1 of 51 documented reentrancy incidents.
BurgerSwap in Context
The BurgerSwap incident joins a class whose largest loss to date is Curve (2023) at $41M.
Prior Reentrancy Before BurgerSwap
The nearest reentrancy incident before BurgerSwap was RariCapital, 18 days earlier on May 9, 2021. The same exploit class surfaced again within the reentrancy attack surface.
BurgerSwap Vulnerability Signature
The primary source categorises the BurgerSwap exploit specifically as “Mathematical flaw + Reentrancy”. This narrower label is entity-specific: it reflects how the BurgerSwap contract failed, rather than the broad reentrancy pattern alone.
Impact & Recovery for BurgerSwap
BurgerSwap Loss Figure
The loss figure for BurgerSwap is not publicly disclosed. The primary source reports the exploit in non-USD terms, so no USD estimate is published here. For reference, the average loss across 51 reentrancy incidents in our archive is $2.87M.
Timeline Since the BurgerSwap Incident
The BurgerSwap exploit occurred 4.9 years ago (1,783 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.
Primary Reference for BurgerSwap
Public post-mortem / on-chain analysis for the BurgerSwap incident: view source.
FAQ
How much did BurgerSwap lose?
The BurgerSwap loss figure is not publicly disclosed. The primary source reports the exploit in non-USD token terms, so no USD estimate is published here.
When did the BurgerSwap hack happen?
The BurgerSwap exploit was recorded on May 27, 2021 — 1,783 days ago.
What type of exploit hit BurgerSwap?
The BurgerSwap 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 BurgerSwap?
Our archive contains 51 documented reentrancy incidents. The BurgerSwap incident is one of them.
How does BurgerSwap compare to the largest Reentrancy attack?
The largest reentrancy incident in our archive is Curve (2023) at $41M. The BurgerSwap loss was not publicly disclosed.
What role does the setup phase play in the payment channel?
It initializes the system’s public parameters, including zk-SNARKs and signature parameters, essential for transaction proofs.
How does the study envision the future of Blockchain in enhancing the customer experience in tourism?
By building trust between hosts and guests, and streamlining booking and payment processes.