Bitget CEO Gracy Chen says the attacker behind the exchange’s roughly $388 million security incident first tested its withdrawal controls with two small transfers before escalating to a much larger theft.
The initial transfers were made at about 6:31 p.m. UTC on September 24, 2026, involving 0.184 ETH from an Ethereum hot wallet and 193 TRX from a Tron hot wallet. Both transactions were below Bitget’s risk-control threshold and did not trigger alerts, according to Chen.
About 30 minutes later, the attacker began sending significantly larger amounts across multiple blockchain networks. Chen said 17 transactions between 6:58 p.m. and 8:09 p.m. UTC involved Ethereum, XRP Ledger, Zcash, BNB Chain, Base, Arbitrum, Optimism and Avalanche, with a combined value of about $361 million.
Key takeaways
- Chen says the attacker used two small transfers to test Bitget’s controls before the larger theft.
- Bitget revised its affected-asset estimate to approximately $387.5 million, commonly rounded to $388 million.
- The exchange says a vulnerability in third-party security infrastructure enabled the attacker to obtain high-level internal credentials.
- Bitget’s reconciliation system detected a major discrepancy at 7:05 p.m. UTC, seven minutes after the first reported large transfer.
- Reports from Mandiant and SlowMist became available on September 30; tracing, recovery and further security work remain ongoing.
- Bitget says its cold wallets were unaffected, private-key compromise was ruled out and its Protection Fund was replenished to more than $300 million.
Small transfers preceded the main attack
In Chen’s interview with The Block, the two early transactions were described as tests that fell below alert thresholds. Once those transfers generated no alerts, the attacker moved to larger transactions.
Bitget’s reconciliation system detected a significant discrepancy at 7:05 p.m. UTC, prompting the exchange to block user-initiated withdrawal requests. This was seven minutes after the first reported major transfer, but approximately 34 minutes after the initial small transfers.
Blocking customer withdrawal requests did not immediately shut down every wallet service. Bitget’s published timeline says wallet withdrawal services, including signing services, were shut down at 9:44 p.m. UTC as part of containment.
Bitget later revised its estimated affected amount from $351.6 million to $387.5 million after incorporating additional transfers involving Zcash and TRON assets. The exchange said the revision reflected more complete accounting of the same incident rather than a separate attack or further transfers after containment.
Third-party security infrastructure provided the entry point
The investigation has provided more detail about how the attacker reached Bitget’s wallet infrastructure. The exchange says the attacker exploited a vulnerability in a third-party security product to obtain internal access credentials.
Those credentials were then used to submit fraudulent withdrawal commands to wallet-related backend systems, causing abnormal transfers to bypass existing controls.
Reports from Mandiant, part of Google Cloud, and blockchain security firm SlowMist became available on September 30. Bitget says both investigations identified compromised third-party security products as enabling unauthorized access to the exchange’s wallet environment.
The incident affected a portion of Bitget’s hot and warm wallet infrastructure. The exchange says its cold wallets were unaffected and that the investigation ruled out private-key compromise.
The attacker also deleted traces associated with the fraudulent commands, according to Chen, complicating the forensic investigation.
“It’s also, in my opinion, the trickiest part,” Chen said, referring to the deletion of traces.
Bitget says the affected systems were isolated and the vulnerability remediated. Its recovery programme and asset tracing continue alongside further security work. The exchange also distinguishes the affected exchange infrastructure from its separate non-custodial Bitget Wallet product, which it says was not affected.
Bitget restores withdrawals and rebuilds its Protection Fund
In Bitget’s updated incident timeline, the exchange says withdrawals were restored in stages following additional security checks.
BTC withdrawals resumed on September 28, followed by ETH on September 29 and USDT on September 30. Other supported assets, fiat withdrawals and peer-to-peer services resumed on October 2, completing the phased restoration plan.
Bitget said the staged approach allowed individual blockchain networks and withdrawal infrastructure to undergo separate security validation.
The financial impact falls within the coverage of Bitget’s Protection Fund, according to the exchange. Bitget said it replenished the fund to more than $300 million on September 30 using company capital.
The exchange also published a proof-of-reserves update based on a September 29 snapshot, reporting an overall reserve ratio of 131% across 19 covered assets. It said every covered asset exceeded the 100% reserve benchmark. These figures describe the assets covered by that snapshot.
Conclusion
The Bitget breach highlights a security risk that extends beyond protecting private keys. According to the exchange and the investigation findings it published, the attacker entered through compromised third-party infrastructure, obtained internal credentials and used them to issue fraudulent withdrawal commands.
The small transfers before the main theft also illustrate how attackers can probe automated controls before escalating. Bitget detected a discrepancy within minutes of the first major transfer, but that detection did not immediately halt all unauthorized wallet activity.
With independent reports now available and recovery work continuing, the next focus is how Bitget strengthens third-party access, administrative permissions and withdrawal verification to prevent a similar attack path.
Related Posts:
Related posts:
- Ethereum Layer-2 Network Base Sets New Daily Record for DEX Trading Volume
- Bahrain’s Rain Crypto Exchange Hit by $14.8M Exploit, Funds Diverted to BTC and ETH
- Elon Musk Reopens Lawsuit Against Sam Altman’s OpenAI: Details
- Supreme Court Greenlights US to Sell $4.4 Billion in Seized Silk Road Bitcoin
- US Spot Bitcoin ETFs Attract Record $479M in Inflows, Hitting 2-Week High














