BBX Token Hack
Incident Overview
On March 20, 2025, BBX Token (BSC) suffered a $12,000 loss due to a liquidity pool manipulation attack exploiting its _transfer() function.
On March 20, 2025, the BBX Token contract on BNB Smart Chain (BSC) was exploited due to a flaw in its _transfer() function, which burned liquidity pool tokens and forced a sync() call on PancakeSwap. The attacker repeated this process 252 times, causing a pool imbalance and manipulating the token’s price. Once the reserves were distorted, they executed a swap via PancakeRouter, extracting value at a favorable rate.
The stolen funds were then laundered through Tornado Cash, making recovery difficult.
Incident Report
Protocol Information
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to BBX Token, these are the critical security checks that could have prevented this incident (March 2025).
- Verify all logic paths related to Other are guarded by proper access controls and input validation
- 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 TrialSecurity Audit History
- Audit Report 1 Report
Sources & References
Learn to Prevent the Next BBX Token
The BBX Token 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.