WebKeyDao Hack

TOTAL LOST $737K
Low Other

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain 2025 Incident surface
Recovered - No recovery reported
All-Time Rank #907 By amount stolen
Protocol Type Exploit/Other Target category

Incident Overview

Quick Summary

On March 15, 2025, WebKeyDao was exploited for ~$737K due to an unprotected buy function in the contract 0xD5110...CD851.

Details of the Exploit

On March 15, 2025, an attacker exploited a vulnerability in WebKeyDao’s smart contract 0xD5110...CD851, which lacked proper protection in its buy function. By using 1,159 BUSD, the attacker minted 230 wkeyDao tokens at a highly favorable rate. These storage values were set using the SetSaleInfo function, modifying storage slots 0x9c and 0x9e, which controlled token pricing.

The attacker then sold the 230 tokens for 13,167 BUSD on a decentralized exchange (DEX), making a 10x profit. Despite the vulnerability, the contract had a 67-token sale threshold, preventing a full drain of the $11M liquidity pool. Initially, the loss was estimated at $73K, but after further analysis, the total stolen funds were confirmed to be ~$737K.

The vulnerable contract is no longer exploitable, and full details have been disclosed to the community.

Incident Report

Protocol / Project WebKeyDao
Date of Incident
Attack Technique Other
Classification Other
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Other
Official Website webkey.pages.dev/
Protocol Twitter/X @WebKey01
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
DAO BNB Chain Ecosystem
Protocol Links

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 WebKeyDao's contract logic - root cause: other
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 WebKeyDao, these are the critical security checks that could have prevented this incident (March 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 Trial

Sources & References

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

DeFiTuna $570K
Other
Cascade $1.3M
Other
Lumi Finance $264K
Other
Hinkal $820K
Other
AIDCToken $121K
Other
Polymarket $3.0M
Other

Learn to Prevent the Next WebKeyDao

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

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial