WSB Coin Hack

TOTAL LOST $635K
Low Rugpull

Summarize with AI

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

Incident Overview

On the 4th of May WSB Coin (WSB) on the Ethereum main net was rugged for approx 635k USD.

The team was responsible for managing tokens in the WSB protocol executed a token dumping scam, causing the project significant losses. One of the team addresses received a substantial amount of tokens by calling the claimWSBModeratorsAllocation() function and sold off the tokens, leading to a sharp drop of around 90% in its initial price.

claimWSBModeratorsAllocation call:

https://etherscan.io/tx/0xef1b6db5…f615b3

Sale example txs:

https://etherscan.io/tx/0x0075880c…a4d7eb

https://etherscan.io/tx/0x5f79dbd0…2c56b8

https://etherscan.io/tx/0xe6d7f1e7…057a7e

https://etherscan.io/tx/0x1289072f…3648ec

Scammer address:

https://etherscan.io/address/0x0ae042d2…fe7894

Incident Report

Protocol / Project WSB Coin
Date of Incident
Attack Technique Rugpull
Classification Token

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token WSB
Official Website wsbcoin.org/
Protocol Twitter/X @WSBCoinOfficial
Team Anonymous
Source Code Unverified

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.

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 WSB Coin'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 WSB Coin, these are the critical security checks that could have prevented this incident (May 2023).

  • 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 WSB Coin

The WSB Coin 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