Raptor2 Hack
Incident Overview
The contract deployer added initial liquidity at:
https://bscscan.com/tx/0x78e7b5eb…2af9d4
The liquidity was removed and tokens were sold by the contract deployer:
https://bscscan.com/tx/0xfbceeb8c…c585f7
Stolen funds were transferred to the external address:
https://bscscan.com/tx/0xef06c291…86bd5d
The funds' recipient deposited stolen funds into Tornado Cash Mixer:
https://bscscan.com/address/0xdaa5e569…f4d34a
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 Raptor2, these are the critical security checks that could have prevented this incident (February 2022).
- 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 TrialSources & References
Learn to Prevent the Next Raptor2
The Raptor2 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.