Incident Overview
POKeFARM smart contract was backed by the proxy contract. The major token pair's liquidity wasn't locked. Because the token contract included minting functionality, the owner has minted 1M POK tokens while avoiding the proxy contract. To confuse the community, the contract deployer sent 500K, 250K, 150K, and 100K POK tokens to some wallets. The recipient exchanged POK tokens for 500 ETH, which he subsequently put in Tornado Cash to hide the trace in the following transactions:
https://etherscan.io/tx/0x1a3b8b06…3d4b9d
https://etherscan.io/tx/0x6ad7bc75…b81378
https://etherscan.io/tx/0xc3134767…3c01ef
https://etherscan.io/tx/0x3477512d…b59e74
https://etherscan.io/tx/0xbba546f6…871a5d
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 POKeFARM, 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 TrialSecurity Audit History
- Audit Report 1 Report
Sources & References
-
01
Source 1 https://archive.ph/H31gM
-
02
de.fi Analysis https://t.me/defiyield_ann/269
Learn to Prevent the Next POKeFARM
The POKeFARM 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.