Deriswap Hack
Incident Overview
The team merely had a Github profile and a Telegram group, without a full-fledged website and documentation. They posted a bogus Quantstamp audit on Github to confuse the community. The project team pointed to an official report by Andre Cronje about a December conversation between Yearn and Sushi to show even more legit intentions. It's a second time, where anon dev teams use bogus Deriswap contracts to replicate Andre Cronje's work.
The contract deployer added initial liquidity at:
https://etherscan.io/tx/0x794fae34…6893ee
The liquidity was removed by the contract deployer at:
https://etherscan.io/tx/0x794fae34…6893ee
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 Deriswap, 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
Source 1 https://t.me/defiyield_ann/297
Learn to Prevent the Next Deriswap
The Deriswap 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.