Reflation Hack
Incident Overview
The contract deployer added initial liquidity at:
https://etherscan.io/tx/0xb52e11e1…1f82af
The contract deployer used hidden minting functionality under the increaseAllowance() function to generate new tokens onto his wallet at:
https://etherscan.io/tx/0xaa141fae…03e3a0
The new tokens were exchanged for ETH 3 times at:
https://etherscan.io/tx/0x6d54fe5e…ff39f0
https://etherscan.io/tx/0xebffb4e0…a3b0d5
https://etherscan.io/tx/0xd70328a7…f64e69
Stolen funds were transferred to the external wallet at:
https://etherscan.io/tx/0xa8fb0d30…fcc00b
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 Reflation, 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 TrialLearn to Prevent the Next Reflation
The Reflation 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.