SHIDAO Hack

TOTAL LOST $180K
Low Rugpull

Summarize with AI

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

Incident Overview

On May 25th, SHIDAO was rug pulled for ~$180K. The project falsified the CertiK audit in order to gain the trust of its customers and lure them to rugpool.

Rug funding address: https://bscscan.com/address/0x1815b580…4C5d7f which distributed BNB for a tx fee, funds approximately 25 other addresses with 0.02 BNB for token sales.

The ShiD tokens are then distributed by the contract https://bscscan.com/address/0xC86D17c7…0Ea9A1 to all the addresses.  After funding completes, the wallets sold their tokens.

Incident Report

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

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token ShiD
Official Website mashida.id
Protocol Twitter/X @SHIIIIDAO
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
BNB Chain Ecosystem

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

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

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