Incident Overview
On December 17, 2024, Decentralized Finance (DCF) suffered a hack that resulted in a loss of approximately $9,000.
The victim contract contains an exchange function that uses PancakeSwap’s v2 pair reserves to determine the DCF/BUSD exchange rate. The attacker first swapped nearly all of the DCF tokens in the victim contract for BUSD. They then performed a large trade on PancakeSwap, manipulating the DCF price to appear artificially low.
Finally, the attacker returned to the victim contract and exchanged a small amount of DCF tokens for a disproportionately large amount of BUSD. By repeatedly taking advantage of the contract’s reliance on the manipulated on-chain price, the attacker walked away with around $9,000 in total.
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 DCF, these are the critical security checks that could have prevented this incident (December 2024).
- Verify all logic paths related to Other 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 DCF
The DCF 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.