CBDAO Hack
Incident Overview
The contract deployer took advantage of a hidden minting backdoor in the SBREE smart contract. SBREE tokens were minted in the amount of 50K tokens and converted to BREE tokens.
Mint transaction:
https://etherscan.io/tx/0x3bf7b06d…1db9d2
Migration:
https://etherscan.io/tx/0xd592c3de…fa4677
The address which received new tokens started to dump them in multiple transactions:
https://etherscan.io/token/0x4639cd8c…1c792f?a=0x85c90f36…1bcf15
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 CBDAO, these are the critical security checks that could have prevented this incident (October 2020).
- 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
-
01
Source 1 https://t.me/coinbreederDAO
- 02
Learn to Prevent the Next CBDAO
The CBDAO 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.