Incident Overview
June 2, 2025 – Tail Metaverse staking contracts were exploited for approximately $88K, primarily through manipulation of NFT-based reward logic. The attacker dumped inflated $tailverse tokens for USDT.
The vulnerable staking contract at 0xf633...ae8 allowed repeated reward collection using the same NFT-like token. The attacker deposited the token, claimed rewards, withdrew it, transferred it to a new wallet, and repeated the loop, effectively farming excessive tailverse tokens. These tokens were later dumped on a USDT pair, leading to ~$88K in losses.
Two contracts were affected, and the main exploit address is 0xd1c58...ed76.
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 Tailverse, these are the critical security checks that could have prevented this incident (June 2025).
- Verify all logic paths related to 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 TrialSources & References
Learn to Prevent the Next Tailverse
The Tailverse 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.