Skip to content
Latest alertPremia options vaults on Arbitrum drained of about $400k-$465k via empty option pools and flash loans
0xCERT
All advisories
High0xCERT-2026-0242·

Gamdom Hot-Wallet Breach

A server intrusion drained crypto casino Gamdom's hot wallets across several chains for roughly $4.2 million in a suspected key compromise.

Vuln-watch · relayed from a public source; see Source & attribution below

Affected chainsEthereumBNB ChainSolanaOther / Multi-chainBitcoinPolygonArbitrumOptimism

Summary

A server intrusion drained crypto casino Gamdom's hot wallets across several chains for roughly $4.2 million in a suspected key compromise.

Incident

  • Victim: Gamdom
  • Date (UTC): 2026-10-13
  • Estimated loss: $4.2M
  • Chain(s): Ethereum, BNB Chain, Solana, Tron, Bitcoin, XRP Ledger, Polygon, Arbitrum, Optimism
  • Attack type: private key compromise
  • Funds status: stolen

Recommended actions

  • If you use Gamdom, move funds to a fresh wallet with a new seed phrase once the vendor confirms the root cause
  • Update the wallet software only from official sources
  • Beware of follow-on phishing: ignore unofficial "refund", "recovery", or "claim" links and DMs; use the project's verified channels only

Source & attribution

Full analysis on Blockchain Breaches, 0xCERT's incident archive: https://www.blockchainbreaches.com/en/breaches/gamdom-2026. Primary sources: https://www.cryptopolitan.com/gamdom-exploit-losses-pegged-at-4-2m-topping-firms-3m-estimate/ ; https://www.igamingrepublic.com/gamdom-temporarily-shuts-down-after-2-3m-leaves-hot-wallets/ ; https://www.kucoin.com/news/flash/gamdom-suffers-security-attack-over-4-2m-stolen-across-multiple-chains ; https://www.thegamblest.com/gamdom-lost-3m-following-security-breach/.

OpenPGP-signed. The signed text of this advisory verifies against the 0xCERT key CCC7 D9EC 9415 723D.

Published 2026-10-13 · last updated 2026-10-15

curl -s https://www.0xcert.com/pgp.asc | gpg --import && curl -s https://www.0xcert.com/advisory/0xCERT-2026-0242/signed.txt | gpg --verify