Shido Hack

TOTAL LOST $3.3M
Medium Private Key Compromised / Access Control ethereum

Summarize with AI

Affected Chain ethereum Incident surface
Recovered - No recovery reported
All-Time Rank #526 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

Access control issue leads to $4M Loss at ShidoGlobal

ShidoGlobal recently encountered a transfer of ownership, resulting in a significant loss amounting to approximately $4 million. The exploit occurred when the new owner swiftly upgraded the StakingV4Proxy contract by introducing a concealed withdrawToken() function. This function enabled the attacker to execute withdrawals of the entire balance of 4,353,473,223.864904 $SHIDO tokens from the contract.

Subsequently, the attacker swapped a portion of the acquired $SHIDO tokens for $ETH and transferred 692.8 $ETH, equivalent to $2.4 million, to address 0x4621e0cd…25c5dd. The remaining $SHIDO tokens, valued at $1.6 million, are still retained in the attacker's address 0x1982358c…d0041f.

Ownership Transfer Transaction:

https://etherscan.io/tx/0xaa76ea50…aafcbe

Attacker's ETH Address:

0x4621e0cd…25c5dd

Incident Report

Protocol / Project Shido
Date of Incident
Affected Chain(s) ethereum
Attack Technique Private Key Compromised / Access Control
Classification Protocol Logic / Other
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Access control
Smart Contract Language Solidity
Official Website shido.io/
Protocol Twitter/X @ShidoGlobal
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Ethereum 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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of Shido's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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 Shido, these are the critical security checks that could have prevented this incident (February 2024).

  • Verify all logic paths related to Private Key Compromised / Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
  • 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

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next Shido

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