YEED Hack

TOTAL LOST $1.0M
Medium Other

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #827 By amount stolen
Protocol Type Exploit/Other Target category

Incident Overview

YEED Token was dumped due to the exploit with a profit of about 1M+ $USD.

The hacker has performed transfers to three trading pairs, namely ZEED, HOR, and USDT via YEED. This process has been repeated multiple times. The ZEED tokens are directly added or subtracted from the balance of the trading pair, which creates a vulnerability that the hacker exploits.

This vulnerability allows the hacker to increase the balance and receive excess rewards from the pair. The attack leverages the ZEED contract's direct calculation of the balance using the rewardFee but not using the separate calculation of zedreward, horward, usdtreward. This vulnerability is used to generate profits for the hacker.

The total amount of funds stolen is estimated at $1,043,070. The hacker has not yet transferred out the funds, as the contract has already self-destructed.

Exploit TXs:

https://bscscan.com/tx/0x05074762…3fa83a

Exploiter address:

https://bscscan.com/address/0xec14207d…6e0fb0

Attacker contract:

https://bscscan.com/address/0x05e55d05…103374

Incident Report

Protocol / Project YEED
Date of Incident
Attack Technique Other
Classification Token

Protocol Information

Protocol Type Exploit/Other
Affected Token YEED
Official Website playseedgo.com/play
Protocol Twitter/X @SeedCombinator
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Communications & Social Media Gaming Sui Ecosystem Telegram Bot Toncoin Ecosystem MoveVM (MVM) Tap To Earn (T2E)

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.

Technical Knowledge Deep understanding of other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in YEED's contract logic - root cause: token
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Other audit checklist and test coverage

If you're auditing a protocol with similar architecture to YEED, these are the critical security checks that could have prevented this incident (April 2022).

  • 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 Trial

Sources & References

Learn to Prevent the Next YEED

The YEED 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.

Recreate exploit patterns safely Free Trial