Is Bitget safe to connect?
Exchange ยท Multi-asset centralized exchange (derivatives, spot). Checked 2026-10-24; every line links its source.
Worst case: Bitget holds your coins: in Sept 2026 a hack froze all withdrawals for 4-8 days, and recovery depended on Bitget's own protection fund; a leaked withdraw-enabled key works from any whitelisted IP.
Safe setup in 3 steps
- Create bot keys with Trade (or Read-only) only and bind them to your server IP
- Never enable Withdraw on a key you hand to a third-party bot or copy-trading tool
- Keep only active trading balance on Bitget and withdraw the rest to your own wallet
Bitget also has a full listing with an Agent Risk Score Agent risk 80% (partial, 6 of 7 inputs): Bitget on TradingAgentStack.
What it can do with your money
| Who holds the keys | The exchange holds your funds Custodial; the Sept 2026 hack drained Bitget hot/warm wallets holding customer deposits. source |
|---|---|
| Can funds be sent out to any address? | Yes. Withdrawals available; they were fully suspended 2026-09-24 and restored in phases 2026-09-28 to 2026-10-02 after the hack. source |
| What a leaked API key can do | Each UID can create 10 API keys, each read-only or read/write, with Read-only, Trade, Transfer and Withdraw permissions. 'You can only withdraw coins through a whitelisted IP address'; binding an IP is 'strongly recommended' for all keys. Key expiry is not stated. source |
| Monero and Zcash | XMR: no spot market; XMR USDT-margined perpetual futures (status 'normal' in Bitget public API on 2026-10-24) ZEC: trade+deposit+withdraw (spot listed 2025-12-03; ZECUSDT spot 'online' in Bitget public API on 2026-10-24) source |
Official links
- Website:
bitget.com
Where we confirmed these
Deadlines
- 2027-07-10: EU AMLR (Regulation (EU) 2024/1624, Art. 79(1)) applies: crypto-asset service providers may not keep accounts that allow anonymisation or obfuscation of transactions, including through anonymity-enhancing coins (e.g. XMR, ZEC). Relevant if you use an EU/EEA-licensed entity of this service. source
Incidents
| Date | What happened | Amount | Outcome | Source |
|---|---|---|---|---|
| 2026-09-24 | Bitget hot/warm wallets drained after attackers used a third-party security product vulnerability to get internal credentials and send fraudulent withdrawal commands (ETH, XRP, BNB, AVAX, USDT, USDC, ZEC, TRX networks) | ~$387.5M (initially $351.6M) | All withdrawals suspended, then restored in phases 2026-09-28 to 2026-10-02; Bitget said its Protection Fund covers the loss and user balances were unaffected | source |