Bitget Hot Wallet Hacked for Approximately $351.6 Million
Gracy Chen, CEO of Bitget, released a security notice: At 18:31 UTC on September 24, the security system detected unauthorized transfers from some hot wallets, estimating the affected funds to be about $351.6 million. She stated that all cold wallets remain secure, and the theft is limited to a portion of the hot and warm wallets within the three-tier architecture; the user protection fund has a balance exceeding $464 million, which can cover all losses. Withdrawals are suspended pending security review, while deposits and trading continue, and account balances remain unchanged, with a commitment to update every hour and a root cause report within 24 hours, without speculating on the attack path until the investigation is complete.
On-chain monitoring appeared before the official announcement. Independent analysis initially observed about $170 million to $183 million transferred from addresses labeled with Bitget to newly created addresses, including assets such as ETH, USDT, USDC, AVAX, BNB, and tokenized gold XAUT; Etherscan labeled the receiving address as Bitget Exploiter 1. Arkham analysis indicated involvement of three hot wallets across three chains and one address labeled as a cold wallet, with funds consolidated into a single address, and stablecoins exchanged for ETH that cannot be frozen by the issuer and bridged across chains. The official total is higher than the early on-chain visible portion, with the difference not detailed in the announcement.
Earlier on the same day, the hot wallet of crypto casino Duelbits was drained of approximately $4.2 million to $7 million, and about $1.8 million USDC was transferred from the Payy bridging contract. The scale of on-chain theft in September has been reported by statistical agencies as the highest monthly figure since 2026. Bitget stated that it has flagged the abnormal addresses and reported to law enforcement and on-chain security companies. If the protection fund is utilized at face value, it will significantly reduce most of the cushion in one go; the decision to suspend withdrawals will determine whether the narrative shifts from on-chain events to account queues.
Mechanically, what is sold is the operational inventory prepared for withdrawals in hot and warm wallets, and what is bought is the authority to simultaneously dispatch multi-chain labeled addresses. The event driver is unauthorized signatures or keys used for withdrawals, not market price fluctuations. Funds moved from the exchange's hot end through exchanges and cross-chain into the attack address; the beneficiary is the party controlling that address, while Bitget is under pressure to fill the gap with the protection fund and to exchange the suspension of withdrawals for review time. User ledgers still show balances, with liquidity temporarily replaced by platform credit. Cold wallets have been declared untouched, effectively tying the repayment narrative to the size of the fund rather than immediate on-chain reserves.
Source: Public Information
ABAB AI Insight
The hot wallets of centralized exchanges come at the cost of withdrawal speed. Bitget has structured its architecture into three tiers: hot, warm, and cold, emphasizing that the theft is "only a part" to reframe the $351.6 million from "the platform being drained" to "the operational layer being compromised." The protection fund of $464 million leaves about $112 million as a buffer against the $351.6 million, numerically sufficient, provided that the fund's assets can be liquidated immediately and there are no overlapping claims. The on-chain report of $180 million and the official report of $350 million indicate that the labeling system and internal accounting do not align, with discrepancies emerging between analysts and officials regarding cold wallet labels, necessitating an explanation in the root cause report.
The capital path is "user deposits - hot wallet float - protection fund commitment." Suspending withdrawals transforms redemption rights into queue rights, while allowing trading lets users hedge risks within the platform. The attacker exchanged USDT and USDC for ETH to evade freezing by the issuer, consistent with the exchange paths of Duelbits and Payy on the same day. Exchange competition relies on withdrawal experience, necessitating sufficiently large hot wallets; if hot wallets are large enough, a single theft can reach hundreds of millions. The theft occurring just before the anniversary compressed the public relations window to a 24-hour report.
Comparing the 2023 Stake hot wallet incident, the 2024 Duelbits incident, and multiple instances of "fund coverage, withdrawal suspension" in exchange scripts: all replace stolen hot ends with off-balance sheet or dedicated account commitments. The difference this time is that the official figure directly approaches three-quarters of the total fund amount, using the cushion thinly in one go. The industry stage remains at a point where multi-chain hot keys can be emptied by the same set of permissions. Whoever can make the warm layer impossible to empty with a single signature can still promise instant withdrawals; whoever treats the protection fund as an insurance policy will be the first to be priced in the next hot wallet incident.
Structural judgments belong to operational risks concentrated before the technical replacement is completed. Pricing power lies between withdrawal speed and key segmentation. The mechanism requires exchanges to have hot assets for redemption, and hot assets must be signed online; if the multi-layer architecture shares control surfaces, the cold wallet narrative cannot prevent the warm layer from moving together. The fund covers accounting losses but cannot mask the trust discount before the withdrawal gate opens.
ABAB News · Cognitive Law
If hot wallets are fast, the amount stolen will be priced according to the exchange's scale.
The protection fund covers the balance sheet but cannot mask the queue from suspended withdrawals.
Stablecoins are first exchanged for ETH, rendering the issuer's freeze key ineffective.