BONK Inu Hack
Incident Overview
BONK Inu fake token was rugged on the Polygon network. The scammers withdrew about $150k USD of USDC from liquidity pairs.
The BONK Inu ERC20 contract contains onlyOwner function with the minting ability. Also, the scammer didn't lock his LP tokens so he did both steps to rug users: 1) remove liquidity from pairs and 2) sell tokens to drain all left liquidity. Estimate losses are about $150k USD.
Scammer address:
https://polygonscan.com/address/0xbcefc34e…bb9e72
Minting tx:
https://polygonscan.com/tx/0xd043614e…cae655
Remove liquidity:
https://polygonscan.com/tx/0x72ddca4c…196202
Sell BONK:
https://polygonscan.com/tx/0xb6f40cd7…c216fe
Transfer USDC to another address:
https://polygonscan.com/tx/0xf64652b1…fe1b0e
https://polygonscan.com/tx/0xd0e7e5fc…7e4f57
https://polygonscan.com/tx/0x5abc0855…5fd074
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 BONK Inu, these are the critical security checks that could have prevented this incident (January 2023).
- 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 TrialSources & References
Learn to Prevent the Next BONK Inu
The BONK Inu 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.