Pump Farm Hack
Incident Overview
The contract deployer interacted with the 3rd party malicious unverified smart contract that received infinite approval for spending the user's approved tokens. He invoked the setMigrator() function at the following transaction:
https://etherscan.io/tx/0xcacef01f…b30864
This contract called migrate() function multiple times. Example transaction:
https://etherscan.io/tx/0x88e788af…42c164
Migrated LP tokens were removed from the liquidity pool at:
https://etherscan.io/tx/0xeb99cfe7…5d3bfe
In addition, the contract deployer has minted 10q PPF tokens onto his wallet:
https://etherscan.Io/tx/0xa7ca31db…699d77
After, 1 billion PPF tokens were exchanged for 220.60 WETH:
https://etherscan.io/tx/0x6d455a00…02c483
Stolen funds were deposited to the Tornado Cash at these 8 transactions to cover up the tracks:
https://etherscan.io/address/0x0ef1a03c…fe1eaa
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 Pump Farm, these are the critical security checks that could have prevented this incident (November 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 TrialSources & References
-
01
Source 1 https://archive.ph/5LVnC
-
02
Source 2 https://archive.ph/iAAAi
- 03
Learn to Prevent the Next Pump Farm
The Pump Farm 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.