GDAO Hack

TOTAL LOST $90K
Low Rugpull

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #1559 By amount stolen
Protocol Type Exit Scam/Rugpull Target category

Incident Overview

GDAO token was rugpulled. The token deployer-related EOA address drained liquidity for 90,302 $USD.

GDAO is a copycat BEP20 token trading on PancakeSwap, and can't be confused with other tokens with the same symbol. The token deployer sent 1,000,000 $GDAO tokens to an EOA address, which drained the liquidity and transferred the stolen funds through TransitSwap. The scammer made a profit of 90,302 $USD.

Scammer addresses:

https://bscscan.com/address/0x7f12728d…6d5d71

https://bscscan.com/address/0xb67b4aa8…878c77

Token transfer transaction:

https://bscscan.com/tx/0xb0ed3561…85dbf3

Incident Report

Protocol / Project GDAO
Date of Incident
Attack Technique Rugpull
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token GDAO
Official Website www.gold-dao.org/
Protocol Twitter/X @gldrwa
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
DAO Tokenized Gold [Deprecated] ICP Ecosystem Internet Computer Ecosystem Real World Assets Protocols DePIN Tokenized Assets Tokenized commodities

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 rugpull 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 GDAO'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? Hard to catch — private key / OpSec failures are outside smart contract audit scope

If you're auditing a protocol with similar architecture to GDAO, these are the critical security checks that could have prevented this incident (October 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 Trial

Sources & References

Learn to Prevent the Next GDAO

The GDAO 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