Carillonium Hack
Incident Overview
The $CAROM project has been rug pulled by the token creator who previously created the rug pull project NeotericFinance.
The scammer deployed a token where 10^15 tokens were minted to his/her address, then scammer created a liquidity pair between CAROM/BNB:
https://bscscan.com/tx/0xd9c9e6a3…4d6272
After a short period of time, scammer removed some of the liquidity, made swap and then removed the liquidity again, gaining a profit of 213.27 $BNB:
https://bscscan.com/token/0x2d1e3be4…44d4a1?a=0x8f0d9acb…2387e4
Scammer address: https://bscscan.com/address/0x8f0d9acb…2387e4
Dumping transaction: https://bscscan.com/tx/0xf56fd7fe…92a969
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 Carillonium, these are the critical security checks that could have prevented this incident (September 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 TrialSources & References
Learn to Prevent the Next Carillonium
The Carillonium 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.