BabyElon Hack
Incident Overview
BabyElon token has been rugged by contract creator for 183.35BNB(~$52,852). Then all tokens were laundered via Tornado Cash.
Token address: https://bscscan.com/address/0x292e89d5…140b43
Contract creator: https://bscscan.com/address/0x999fae84…32a7c1
Attacker created LP pair between 100M BabyElon and 10BNB: https://bscscan.com/tx/0x1d07387a…6acc80.
Then he/she increased the LP pool by adding 290BNB and 2.9B BabyElon thereby artificially provoke a sharp rise in prices: https://bscscan.com/tx/0xfac7fa93…2bc03e
After part of BabyElon was bought, attacker removed LP having received 484.35BNB of which the profit was 183.35BNB: https://bscscan.com/tx/0xa3974709…d4feff
Then tokens were transferred to https://bscscan.com/tx/0xd25a56ea…9fb821
All tokens were laundered via TornadoCache.
Incident Report
Protocol Information
Market Context at Time of Hack
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 BabyElon, these are the critical security checks that could have prevented this incident (June 2022).
- Verify all logic paths related to Rugpull 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 TrialLearn to Prevent the Next BabyElon
The BabyElon 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.