Incident Overview
The dragonball token was exploited via flashloan attack on the 8th of Feb. The profit is about 16k USD.
The Dragonball token was hacked using a flashloan. The attacker took a flashloan of 1300 BNB and exploited the reflection rate mechanism, gaining the ability to withdraw a profit of 54.92 BNB, equivalent to $15,912.69.
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 Dragonball, these are the critical security checks that could have prevented this incident (February 2023).
- Verify all logic paths related to Flash Loan Attack are guarded by proper access controls and input validation - see the Flash Loans 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
- 01
-
02
Web Archive https://archive.ph/wip/C1G96
Learn to Prevent the Next Dragonball
The Dragonball 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.