Incident Overview
DEFIBase is a fork of the Base project. There was an error when calling the rebase function, which returned the current token price as opposed to the initial one. With a manual call to the price rebase method, the developers failed 280 transactions. The Telegram chat was muted for the community. 696 ETH was withdrawn from the general pool in a series of transactions.
Victims' negative comments:
https://etherscan.io/address/0xfda2dca8…bac1a3#comments
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 DEFIBase, these are the critical security checks that could have prevented this incident (December 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 TrialSecurity Audit History
- Audit Report 1 Report
Sources & References
- 01
-
02
de.fi Analysis https://t.me/defiyield_ann/297
- 03
Learn to Prevent the Next DEFIBase
The DEFIBase 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.