GoldenFarm Hack
Incident Overview
The contract deployer added initial liquidity multiple times, the example transactions:
https://www.bscscan.com/tx/0x6f07974c…33536c https://www.bscscan.com/tx/0xf179f346…d6400a https://www.bscscan.com/tx/0xef73a1d9…294b5b
Tokens were sold multiple times by the contract deployer:
https://www.bscscan.com/address/0xac6f6ca3…e1b83e
The liquidity was removed multiple times as well, the example transaction:
https://www.bscscan.com/tx/0xe0d3a678…00ddf1 https://www.bscscan.com/tx/0xf06b9d42…dfc57e
The stolen funds were bridged to the Binance Chain via BSC: Token Hub by the contract deployer at:
https://www.bscscan.com/tx/0xd3be69e4…716b72
https://www.bscscan.com/tx/0xd37703dc…6e9561
https://www.bscscan.com/tx/0xaa159255…022fc4
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 GoldenFarm, 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 TrialSources & References
-
01
Source 1 https://app.goldenfarming.org/
Learn to Prevent the Next GoldenFarm
The GoldenFarm 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.