BurgerSwap Hack

TOTAL LOST $7.2M
Medium Flashloan Reentrancy Attack / Flash Loan Attack binance bsc

Summarize with AI

Affected Chain binance 2 chains affected
Recovered - No recovery reported
All-Time Rank #368 By amount stolen
Protocol Type Dexs Target category

Incident Overview

An attacker exploited BurgerSwap using flash loans and a fake token, resulting in a loss of $7.2 million.

The attacker initiated a flash swap of 6k WBNB ($2M) from PancakeSwap, which was then swapped for 92k BURGER on BurgerSwap. The attacker then created a non-standard BEP-20 token and formed a new trading pair with BURGER. Using this pair, the attacker swapped 100 fake tokens for 4.4k WBNB, and then swapped 45k BURGER for another 4.4k WBNB.

The attacker then swapped 493 WBNB for 108.7k BURGER on BurgerSwap, before finally repaying the flash swap.

The attacker's transaction:

https://bscscan.com/tx/0xf598e092…1baa1d

Incident Report

Protocol / Project BurgerSwap
Date of Incident
Affected Chain(s) binance bsc
Attack Technique Flashloan Reentrancy Attack / Flash Loan Attack
Classification Ecosystem / Exchange (DEX)
Primary Source View Post-Mortem

Protocol Information

Protocol Type Dexs
Affected Token BURGER
Official Website burgerswap.org/
Protocol Twitter/X @burger_swap
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Arbitrum Ecosystem

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 flashloan reentrancy attack / flash loan attack and Solidity and EVM internals
Capital Required Flash loan capital (borrowed atomically, zero upfront cost)
On-Chain Access Ability to interact with binance, bsc smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in BurgerSwap's contract logic - root cause: ecosystem / exchange (dex)
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? Yes — skilled auditors routinely flag Flashloan Reentrancy Attack / Flash Loan Attack vulnerabilities in code review

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

  • Verify all logic paths related to Flashloan Reentrancy Attack / Flash Loan Attack are guarded by proper access controls and input validation - see the Flash Loans Attacks attack class for patterns
  • Check that all state-changing functions follow the Checks-Effects-Interactions (CEI) pattern to prevent reentrancy and logic ordering bugs
  • 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

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Flash Loans Attacks examples →

Proof-of-Concept Exploits

1 PoC available

On-Chain Evidence & References

Sources & References

Learn to Prevent the Next BurgerSwap

The BurgerSwap 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