Toutes les vulnérabilités
CRITICALWeb3

WEB3-MIXIN-NETWORK-2023

Web3 · Ethereum · Mixin Network

Résumé

On September 23, 2023, Mixin Network lost about $200M (roughly $95M ETH, $24M BTC and $24M USDT among other assets) after attackers breached the database of the network's third-party cloud service provider, which held Mixin's deposit-address and hot-wallet private keys in a recoverable manner. With the database compromised, the attacker reconstructed the private keys and signed outbound transactions directly, sweeping over 11,400 deposit wallets from highest to lowest balance across more than 10,000 transactions; stolen USDT was swapped to roughly 23.5M DAI to break traceability. The weak link was the upstream cloud database acting as a single point of failure with recoverable keys, rather than a smart-contract bug or a direct private-key theft from Mixin itself (the provider is widely inferred to be Google Cloud but was never officially confirmed). Mixin engaged Google and SlowMist to investigate, suspended deposits and withdrawals, offered a $20M bounty, and announced a plan to reimburse 50% of affected user assets with the remainder issued as debt/bond tokens. The bulk of the funds was laundered and not recovered.

Comment l’éviter dans votre code

  • Never store private keys recoverably in a database; use HSM or threshold/MPC signing so keys are never reconstructable.
  • Segregate and independently audit third-party cloud infrastructure that touches custody.
  • Apply least privilege and strong isolation between application databases and key material.
  • Monitor for bulk sequential outflows and automatically halt withdrawals on anomalous sweeping patterns.
  • Encrypt key material at rest with hardware-backed keys and enforce strict access logging on the provider.

Références

Vulnérabilités liées

Tout Web3 →