Incident Overview
On February 11, 2025, Four.Meme suffered an exploit, leading to a loss of approximately $183K. In response, the token LP on PancakeSwap was temporarily suspended to prevent further damage.
The attack targeted four_meme_’s liquidity pool (LP) on PancakeSwap, prompting the team to pause trading to prevent further losses. On-chain trading remained unaffected, and internal funds were not compromised. The development team is currently working on a fix, after which the LP will be reopened.
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 four.meme, these are the critical security checks that could have prevented this incident (February 2025).
- Verify all logic paths related to Liquidity Pool Exploit / Other 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
Proof-of-Concept Exploits
On-Chain Evidence & References
Sources & References
Learn to Prevent the Next four.meme
The four.meme 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.