Toutes les vulnérabilités
CRITICALWeb3

WEB3-POLONIEX-2023

Web3 · CEX · Poloniex

Résumé

On November 10, 2023, the Justin Sun-linked exchange Poloniex lost roughly $120 million (estimates ranged $114 to $126 million) after attackers compromised a hot-wallet private key and swept tokens to attacker-controlled wallets. The drain hit a hot wallet labeled 'Poloniex 4,' with automated bots executing hundreds of unauthorized transactions that emptied multiple assets in just over an hour, a pattern indicating the signing key itself was in attacker hands rather than any contract bug. The exact intrusion path was not disclosed, but single-key-controlled hot wallets with inadequate signing thresholds let one compromised key authorize the mass outflow. Analysts including Elliptic attributed the theft to North Korea's Lazarus Group based on the attack methodology and a laundering signature of splitting token types across addresses before consolidating, and Justin Sun publicly linked the perpetrators to Lazarus. Poloniex offered a white-hat bounty for the funds' return; the attacker began moving funds (including ETH to Tornado Cash) and the bulk was not recovered, though Sun said losses would be reimbursed.

Comment l’éviter dans votre code

  • Keep the bulk of assets in cold storage; limit hot-wallet balances to operational float.
  • Use MPC/threshold signing or multisig so no single key can authorize withdrawals.
  • Store keys in hardware security modules with least-privilege, segregated infrastructure.
  • Deploy withdrawal rate limits, allowlists, and anomaly detection to stop bot-driven mass drains.
  • Add independent transaction signing review for high-value or bulk outbound transfers.

Références

Vulnérabilités liées

Tout Web3 →