Incident Overview
46.6M LYM were dumped on Pancakeswap by the attacker.
The attacker received 46.6M LYM tokens from a proxy contract with unverified implementation (0xbC8054Ab…6D9679) through calling the claimStaticReward() function. All the received tokens have been sold off on the DEX.
The attacker address:
https://bscscan.com/address/0x00e6392f…d6993e#tokentxns
The attack transaction:
https://bscscan.com/tx/0x8fc7dce6…e03a92
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 Lymex, these are the critical security checks that could have prevented this incident (December 2022).
- 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
-
02
Web Archive https://archive.ph/x8GZL
Learn to Prevent the Next Lymex
The Lymex 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.