All vulnerabilities
CRITICALWeb3

WEB3-STAKE-COM-2023

Web3 · CEX · Stake.com

Summary

On or about September 4, 2023, crypto gambling platform Stake.com lost about $41 million across Ethereum, BNB Chain and Polygon after attackers gained the ability to make unauthorized transactions from its hot wallets. The exact mechanism is disputed: co-founder Edward Craven stated private keys were not compromised and blamed a sophisticated breach of the platform's transaction-authorization service, whereas multiple security researchers (Cyvers, others) assessed a hot-wallet private-key leakage as the most plausible explanation given the clean, MEV-free on-chain sweep. Either way, the weakness was operational, signing authority over internet-connected hot wallets was reachable by the attacker, not a smart-contract flaw. On September 6, 2023 the FBI officially attributed the theft to North Korea's Lazarus Group (APT38), tracking the stolen funds as they moved into various virtual-currency addresses; Elliptic observed commingling with Atomic Wallet proceeds. The funds were laundered and not recovered.

How to avoid it in your code

  • Use MPC/threshold signing or multisig so no single key or service can authorize withdrawals.
  • Keep the bulk of assets in cold storage; minimize hot-wallet balances.
  • Harden and segregate the transaction-authorization service with least-privilege access.
  • Protect signing keys in hardware security modules and rotate them regularly.
  • Add withdrawal allowlists, rate limits, anomaly detection, and independent signing review.

References

Related vulnerabilities

All Web3 →