MoltenSwap Hack
Incident Overview
The Master Chef contract contains hidden functionality under the set() function, which was invoked multiple times by the contract deployer at:
https://explorer.bitquery.io/bsc/txs/calls?internal=false&contract=0xb9c56744…3e7070&method=d9638422
Calling set() function led to the LP tokens transfer onto the external wallet, example transaction:
https://bscscan.com/tx/0x3b8ed32a…53de91 (at the bottom of the list)
The liquidity was removed by the external wallet multiple times at:
https://bscscan.com/tx/0x31c99d77…e84d55
https://bscscan.com/tx/0xde655409…4887cc
https://bscscan.com/tx/0x6c9d7e8b…e4de6b
https://bscscan.com/tx/0x21d2c374…e69a10
https://bscscan.com/tx/0x3a0c56b9…8cb1bb
https://bscscan.com/tx/0xdcd892c2…81b640
https://bscscan.com/tx/0x9033ed6a…9f1865
https://bscscan.com/tx/0x0deb3c97…d73e5e
https://bscscan.com/tx/0x53a1f15d…7da8e0
Incident Report
Protocol Information
Market Context at Time of Hack
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 MoltenSwap, these are the critical security checks that could have prevented this incident (March 2021).
- 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 MoltenSwap
The MoltenSwap 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.