Incident Overview
The contract owner could disable the transfer function, which restricted users in selling their tokens.
The contract deployer added initial liquidity at:
https://bscscan.com/tx/0x31fa716c…c54e14
The liquidity was removed by the contract deployer:
https://bscscan.com/tx/0x3ae83336…b0c2ea
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 Q DAO Governance token v2.0, these are the critical security checks that could have prevented this incident (March 2021).
- Verify all logic paths related to Honeypot are guarded by proper access controls and input validation - see the Dao Governance Attacks attack class for patterns
- 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 TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next Q DAO Governance token v2.0
The Q DAO Governance token v2.0 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.