Bitget $387.5M Hack Traced to Third-Party Zero-Day
Attackers were inside Bitget for 25 days before draining hot and warm wallets across 11 blockchains, investigators SlowMist and Mandiant say.
Cryptocurrency exchange Bitget has confirmed that the attackers who stole $387.5 million on September 24 got in through a zero-day vulnerability in third-party security software, The Hacker News reports.
Timeline of the attack
Interim findings from SlowMist and Mandiant show the attackers had a foothold long before any money moved:
- August 31: a service on a third-party security product ("Product A") is compromised through a zero-day. A hidden script reads a database password from an environment variable, according to SlowMist.
- September 23–25: the same activity appears on two more nodes.
- September 24, around 18:31 UTC: the attacker logs in with an internal employee's identity and uses a custom withdrawal tool that forged risk-control parameters. Funds drain for 2 hours and 52 minutes, Bitcoin.com reports.
That 25-day gap between initial access and the theft is the most alarming detail. The attackers spent weeks mapping the exchange's internal systems, learning how withdrawals were approved and building a tool specifically to defeat them. By the time money moved, every step looked legitimate to Bitget's own controls.
No private keys were stolen. Instead, the attackers made withdrawals the exchange's own systems accepted as valid, obtaining high-level internal credentials and using them to issue fraudulent withdrawal commands that bypassed existing risk controls, Bitget said in a follow-up statement (The Hacker News).
Scale of the theft
The theft hit 11 blockchains including Ethereum, XRP Ledger, Zcash, TRON, Arbitrum, Optimism, Base, BNB Smart Chain, Avalanche, Algorand and Celestia (The Hacker News). Bitget initially estimated the loss at roughly $351.6 million before revising the figure upward to $387.5 million — a $35.9 million increase that the exchange said reflected a more complete reconciliation of transactions, including assets on Zcash and TRON that were missing from the first estimate, not additional theft (Cointribune). Only about $632,700 has been frozen by Circle, Tether and NEAR Intents — a small fraction of the total, illustrating how quickly stolen crypto disperses beyond reach once it starts moving across chains.
Bitget's cold wallets and its separate Bitget Wallet app were not affected.
How Bitget recovered
Bitget's Protection Fund, a reserve pool created in January 2022 with 5,500 BTC and a stated minimum value of $300 million, absorbed the loss. CEO Gracy Chen said the fund held more than $464 million before the breach and dropped to around $200 million afterward (CryptoTimes). On 28 September, Chen pledged to restore the fund to more than $300 million within a week using company capital; on 30 September, Bitget announced the fund had been replenished to roughly $309 million, holding 3,705 BTC — 1,795 fewer bitcoin than before the breach, reflecting that the fund is now smaller in bitcoin terms even though its dollar value has been restored above the stated floor (Altcoin Buzz; CryptoTimes).
Withdrawals resumed in phases: Bitcoin, Ether and USDT withdrawals came back first, with the exchange announcing that all remaining tokens, fiat and peer-to-peer withdrawals would resume by 2 October 2026 (Cointribune). Bitget's 30 September Proof-of-Reserves snapshot reportedly showed reserve ratios above 100% across all 19 listed assets, including 142% for BTC, 110% for ETH, 107% for USDT and 154% for USDC (CryptoTimes). Bitget also launched a bounty program offering 5% of any frozen funds and 5% of any recovered funds to incentivize their return (Cointelegraph).
Chen told Cointelegraph that the exchange had not ruled out any possible culprits, including the possibility of an inside job as well as North Korean state hackers (Cointelegraph).
The North Korea connection
Analytics firm Elliptic linked the attack to North Korea, saying it pushes the country's crypto thefts this year past $1 billion, Bloomberg Law reported. If the attribution holds, Bitget joins a long list of exchanges hit by North Korean operators, who have made crypto theft a significant source of hard currency for the sanctioned state. Their playbook has evolved: rather than attacking cryptography directly, they target the people and software around it — fake job applicants, compromised vendors, poisoned updates and, as here, flaws in the security products an exchange relies on.
Why it matters
The security products meant to protect Bitget became the way in. It is the same lesson as the 2025 Bybit theft: attackers no longer need to crack wallet keys if they can control the systems that approve withdrawals. Every vendor with access to your environment is part of your attack surface, and a zero-day in one of them can undo millions spent on your own defenses.
For the wider industry, the incident will renew pressure on exchanges to publish real-time proof of reserves and to treat third-party software with the same suspicion they apply to external attackers.
What a zero-day in a "security product" actually means
It can seem counterintuitive that the tool meant to protect an exchange became the attacker's way in, but this pattern is increasingly common. Security software — endpoint protection agents, monitoring tools, risk-control systems — typically runs with elevated, trusted privileges deep inside an organization's infrastructure, precisely so it can see and respond to threats. That same privileged access makes such software an extremely high-value target: a flaw that lets an attacker run their own code inside a security product can hand them a foothold with far more reach than compromising an ordinary employee laptop. This is part of why security researchers increasingly argue that vendor risk management — vetting, monitoring and limiting the privileges granted to third-party software — deserves the same priority as an organization's external-facing defenses.
What crypto users should do
- Keep long-term holdings in a wallet you control, not on an exchange.
- Spread funds across services rather than holding everything in one place.
- Ignore "Bitget refund" messages — they are a common follow-up scam after large hacks.
- If you trade actively, enable withdrawal address allowlisting and every available verification step on your account.
- Check an exchange's published Proof-of-Reserves data periodically if you keep significant funds there, and understand that a protection fund, while reassuring, is not an unlimited guarantee.
What readers should do
- If you held funds on Bitget during the incident, check official Bitget channels directly (not links from email or social media) for confirmation of your account status and any compensation process.
- Be skeptical of unsolicited "Bitget hack compensation" messages, which scammers commonly send after high-profile exchange hacks to phish for wallet credentials or seed phrases.
- Review your own exchange withdrawal settings, including enabling address allowlisting and withdrawal delays where available, since these controls can blunt the impact of a compromised internal credential even on the exchange's side.
- Diversify custody of significant crypto holdings between a self-custodied wallet and any exchange, so that a single platform's security failure cannot expose your entire portfolio.
- Follow verified updates from Bitget, SlowMist or Mandiant rather than secondhand social media claims, since investigation findings in major hacks are frequently revised as forensic work continues.
Sources & Verification
Additional reporting
- The Hacker Newsthehackernews.com
- Cointelegraph – zero-day investigationcointelegraph.com
- Bitcoin.com Newsnews.bitcoin.com
- Bloomberg Lawnews.bloomberglaw.com
- Cointelegraph – protection fund and operations updatecointelegraph.com
- Altcoin Buzzaltcoinbuzz.io
- CryptoTimescryptotimes.io
- Cointribunecointribune.com



