Toutes les vulnérabilités
CRITICALWeb3exploited in the wild

WEB3-BYBIT-2025

Web3 · CEX · Bybit

Résumé

On February 21, 2025, Bybit lost roughly $1.5 billion (about 401,347 ETH plus stETH/mETH) in the largest crypto hack to date. The root cause was a supply-chain/front-end compromise: a breached Safe{Wallet} developer machine let attackers inject malicious JavaScript into the Safe UI served from Safe's S3-backed app.safe.global front end. The code was scoped to activate only for Bybit's cold-wallet Safe (and one other contract), so when the three signers reviewed a routine cold-to-hot transfer the UI showed legitimate data while their Ledgers were sent a different payload. Signers blind-signed a delegatecall (operation=1) to an attacker contract that, executing in the proxy's storage context, overwrote storage slot 0 (the masterCopy/singleton pointer) with an attacker-controlled implementation, after which sweep functions drained the wallet. The FBI and TRM Labs attributed the theft to North Korea's Lazarus Group (TraderTraitor/APT38); funds were rapidly laundered and not recovered.

Comment l’éviter dans votre code

  • Harden Safe{Wallet} and wallet-UI supply chains: SRI on hosted scripts, integrity-verified CDN assets, and least-privilege developer machine access.
  • Mandate clear-signing and on-device transaction parsing so signers verify calldata, operation type, and target on the hardware wallet, never blind-sign.
  • Independently simulate every multisig transaction (e.g. Tenderly) on isolated infrastructure and compare results before approval.
  • Alert on or block delegatecall (operation=1) and any masterCopy/singleton/implementation change in Safe transactions.
  • Segment and monitor signer endpoints; require multiple independent reviews of decoded calldata from out-of-band channels.

Références

Vulnérabilités liées

Tout Web3 →