From nearly 400 million dollars stolen to the resumption of withdrawals and the flow of funds back in, only a few days have passed in between.
Written by: WhiteRunner
In recent years, it has not been uncommon for exchanges to encounter large-scale security incidents. The attack vectors have gradually extended from hot wallets and signature systems to internal permissions and third-party services. As systems become increasingly complex, the boundaries that exchanges need to defend are also growing larger.
On September 25, Bitget faced a security incident, ultimately confirming that approximately 388 million dollars in assets were affected. CEO Gracy Chen subsequently stated in a live broadcast that this was the first security incident of this kind in the platform's eight-year operation. According to the investigation results released by SlowMist, the earliest malicious activity involved a zero-day vulnerability on a node of a third-party security product. Both Mandiant and SlowMist's investigations pointed to the attack path leading to the compromise of third-party security infrastructure, eventually entering Bitget's wallet environment.
Following the incident, Bitget announced that losses would be covered by the user protection fund. At the time of the incident, this fund, established in 2022, held 5,500 BTC, worth over 464 million dollars. Gracy pledged that the protection fund would be replenished back to 300 million dollars within a week after use, restoring it to the benchmark size set when it was established in 2022. On September 30, this commitment was fulfilled as scheduled.
Withdrawals also began to resume according to the previously announced schedule. At 16:00 on September 28, BTC was the first to open for withdrawals, and after ETH resumed withdrawals on the 29th, the relevant hot wallet quickly turned from net outflow to net inflow. Soon, the balance even slightly exceeded the initial level before the withdrawal opening, indicating that users' trust was returning. As of the publication date, all cryptocurrencies had resumed withdrawals.
From nearly 400 million dollars stolen to the resumption of withdrawals and the flow of funds back in, only a few days have passed in between. How did hackers manage to transfer assets without leaking the private key? How did a protection fund that was prepared for four years come into play? What did Bitget do to turn the tide of the incident?
Hackers Exploit Zero-Day Vulnerability to Compromise Third-Party Security Product
What makes this attack particularly unusual is that Bitget's private keys were not leaked, the cold wallets were not compromised, and it was not a smart contract vulnerability. The breakthrough point that hackers found was a third-party security product used by the platform.

According to the investigation results currently disclosed by Bitget, around 02:31 Beijing time on September 25, the earliest confirmed relevant small transactions appeared on-chain, followed by larger-scale asset transfers.
Gracy stated in an interview with The Block that from 02:58 to 04:09, the attackers made 17 large transactions across multiple networks including Ethereum, XRP, Zcash, BNB Chain, Base, Arbitrum, Optimism, and Avalanche. With subsequent statistics added, Bitget ultimately confirmed that this incident affected approximately 388 million dollars in assets.
At 03:05, about seven minutes after the first large transfer occurred, Bitget's reconciliation system detected a significant financial discrepancy and triggered a platform-wide withdrawal halt; at 03:14, the platform initiated the highest level of emergency response. As it could not be ruled out that the private key had been compromised at that time, the wallet team subsequently transferred the assets to the cold wallet and disabled wallet withdrawals and signing services.
After that, the security team confirmed the root cause of the incident. According to the currently disclosed attack chain, the hackers exploited an unknown zero-day vulnerability in a third-party security product.

A zero-day vulnerability refers to a security flaw that has not yet been known to manufacturers and users, and for which there are no available patches to deploy in advance. In other words, this was an unknown attack entry point. What happened next is key to understanding the nearly 400 million dollars in losses.
Utilizing this vulnerability, the attackers stole internal network credential privileges through the vulnerabilities of the third-party security product, forged withdrawal commands to the wallet system, deceiving the wallet into executing abnormal transfers that bypassed risk verification. Throughout the process, the private key was not leaked, and cold wallets were not affected.

Gracy later also revealed that after completing the operation, the attackers deleted some relevant traces, making it harder to investigate and restore the attack process.
Bitget subsequently disabled the affected third-party functionalities, reissued internal credentials, revoked and re-split high-sensitivity privileges, and increased independent verification for withdrawals. Mandiant and SlowMist are currently still involved in independent forensic investigations and fund tracking.
This incident has left a direct warning for the industry: the security boundaries of exchanges are no longer just about private keys and cold wallets. Security software, wallet infrastructure, and other third-party services that can access core systems may also become attack vectors.
Protection Fund Begins to Be Utilized, Withdrawals Resume According to Schedule
After the incident, the true test of an exchange is how management faces the loss and reassures users.
Bitget was the first to utilize the protection fund.
This fund was established in 2022 and has long maintained a benchmark size of 300 million dollars. At the time of the incident, the fund held 5,500 BTC, valued over 464 million dollars, enough to cover the confirmed losses of approximately 388 million dollars.
Bitget subsequently clarified that the financial impact of this incident would be borne by the protection fund, and user account balances would not be affected.
Before BTC resumed withdrawals on September 28, on-chain activity already showed that the protection fund began allocating assets to the hot wallet. On-chain analyst Ai Yi detected that initially, 2,042.28 BTC was transferred from the related protection fund address into Bitget's hot wallet (Bitget protection fund on-chain monitoring).
This is one of the most commendable aspects of Bitget’s handling of this situation for the industry to consider.
This protection fund was not a temporary compensation plan announced after the incident occurred, but was established four years ago. Funds were long-term reserved, wallet addresses public, and there was a clear scale benchmark; after an actual incident happened, the fund was truly utilized and replenished afterward according to the original standard.
The protection fund resolved the issue of who bears the loss. This time, the nearly 400 million dollars in losses were ultimately not passed on to the users. Gracy stated that Bitget would replenish the protection fund back to at least 300 million dollars within a week, and according to on-chain monitoring, this commitment has been fulfilled as scheduled.

On September 30, Bitget also published its 47th proof of reserves (PoR), with a total reserve ratio of 131%, covering 19 types of assets. Among them, the reserve ratios for BTC, ETH, USDT, and USDC were 142%, 110%, 107%, and 154%, respectively.

Apart from funds, Bitget's communication methods during these days are also noteworthy.
Gracy responded continuously for about three hours in a live broadcast aimed at the community, and CEO Xie Jiayin also kept updating progress through social media and the community. The three-hour live broadcast itself is not the focus; more importantly, during the most chaotic days of the incident, the management consistently stood at the forefront to respond to issues.

Moreover, several key statements basically provided clear information or next steps.
It was quickly made clear that the losses would be covered by the protection fund; after adjusting the impact amount from 351.6 million dollars to 388 million dollars, the reasons for the change were explained; before confirming the attack entry point, there was no rush to conclude on the attackers’ identity and attack methods; and after making progress in the investigation, details about the third-party security product, zero-day vulnerabilities, high-privilege credentials, and forged withdrawal commands were gradually disclosed.
The resumption of withdrawals was the same.
This incident involved multiple cryptocurrencies and networks, and the scope of the investigation was not limited to one wallet. Bitget did not restore all withdrawals at once but opened them in batches after confirming relevant wallets, networks, and eliminating risks.
On September 26, the platform announced a specific recovery schedule: restoring BTC on September 28, restoring ETH and related networks on September 29, restoring USDT and related networks on September 30, and other tokens, fiat currencies, and C2C services scheduled to resume on October 2. Before the publication, all were verified to have been restored as planned.

Considering that this was a major security incident involving multiple cryptocurrencies, various networks, third-party software, and internal permissions, it is commendable to first provide a specific date and time for the recovery plan and then fulfill it item by item.
The preparation of the protection fund four years in advance, its actual utilization after the incident occurs; management continually facing the community; timely disclosure of confirmed information while not rushing to conclude on uncertain information; providing a clear recovery plan with specified times and executing accordingly.
This series of clean and decisive actions has made many people view Bitget more positively.
Signs of a Turning Point Are Emerging, Funds Are Flowing Back In
On September 29, after ETH resumed withdrawals, a noteworthy change quickly appeared on-chain.

According to on-chain analyst Ai Yi, the relevant hot wallet that Bitget prepared for ETH withdrawals saw its balance return to over 30,000 ETH, surpassing the initial value, within half an hour after the withdrawals opened.
Subsequent data released by Bitget showed that in the first hour after resuming withdrawals, about 9,674 ETH flowed in and about 9,023 ETH flowed out, resulting in a net inflow of approximately 651 ETH. Data from September 30 indicated that the total inflow of funds on the platform reached 231 million dollars in 24 hours, close to the daily average inflow of 245 million dollars in August, and there was no one-way capital outflow as previously worried by the market. Instead, signs of renewed confidence in the market could be seen.
At the same time, to reward user trust, Bitget also began launching multiple incentive activities.

ETH PoolX offered a reward pool of 500,000 USDT, and users can participate in the distribution by locking ETH, with early estimates for APR reaching about 37.11%, which then dynamically decreased as participation funds increased.
BTC PoolX was subsequently launched, providing a reward pool of 100,000 BGB and offering extra bonuses based on users' BTC holdings over the previous 15 days.
For stablecoins, Bitget simultaneously launched USDT and USDGO savings activities, supporting flexible deposits and withdrawals, with time-limited APR of 10% and 12%, respectively. The “Peer Program” included 30% of trading fee income from qualified transactions as part of the user awards pool during the activity period, with 60% allocated based on trading volume and 40% based on asset volume. On October 2, Bitget's official data indicated that the first batch of rewards had been distributed, totaling 1,907,455 USDT to 763,543 users.
The intention behind these activities is not hard to understand. The resumption of withdrawals solves the users' concern about "whether they can withdraw," while the subsequent series of activities aim to restart trading, wealth management, and capital accumulation.
Quickly, many users voted with their funds, showing confidence in Bitget and enthusiasm for the activities.

A few days ago, the market was most concerned about "when can I withdraw my funds"; with the resumption of withdrawals, the question began to change to "which activity can yield a higher APR."
Signs of a turning point in the incident.
For exchanges, the most direct proof of restored user confidence is the willingness to keep money on the platform when they can freely come and go.
A Security Incident: What Has It Left for the Exchange Industry?
After the incident at Bitget, it received support from almost "half of the industry."
Most notably, there is Bybit.
In February 2025, Bybit experienced a security incident involving about 1.4 billion dollars. About five hours after the attack, Bitget provided Bybit with 40,000 ETH, valued at over 100 million dollars at that time. This 40,000 ETH was provided without interest, collateral, or a fixed repayment deadline. Bybit subsequently returned the entire amount within three days.
More than a year later, the positions of the two have reversed. After the incident at Bitget, Bybit CEO Ben Zhou quickly expressed a willingness to provide assistance and specifically mentioned: "When we were attacked, Bitget had helped us." Later, Bybit included the relevant stolen funds in the LazarusBounty system for tracking.
More than just Bybit stepped up. CZ publicly voiced support after the incident, and Binance's security team later began to collaborate with Bitget, including sharing threat intelligence, tracking stolen funds, and supporting asset recovery; MEXC CEO Vugar Usi also proactively contacted Bitget to express support. Beyond exchanges, Mandiant and SlowMist participated in investigations and forensics, while Circle and Tether participated in relevant asset freezes.

Seeing these news, I indeed felt a surge of emotion.
The crypto industry has never lacked competition. Exchanges compete for users, liquidity, and market share, but when faced with security crises involving hundreds of millions of dollars, industry peers band together for support.
And whether Bitget, as a platform, has truly earned trust and respect in the industry becomes most evident in times of crisis.
However, if this matter is only confined to "true feelings are revealed in hardship," it underestimates its significance.
The crypto industry lacks a unified institution to cover losses, but protection funds, peer collaboration, security agencies, and on-chain tracking are forming their own risk management networks. Meanwhile, the boundaries that exchanges need to defend are becoming ever larger, from hot wallets and signature systems to third-party software and internal permissions: attacks are becoming increasingly complex, and the industry needs to work together to respond.
Establishing protection funds, maintaining transparency and adherence to commitments afterward, and collaborating within the industry have now become an excellent model for crisis response, and Bitget has now demonstrated this seriously.

For the past two years, the crypto industry has been talking about Mass Adoption. ETFs, stablecoins, RWAs, and tokenized securities have brought in more traditional financial capital, and the regulatory framework in the U.S. is gradually being established. Having reached this point, the industry needs to prove not only innovation and growth but also risk management capabilities.
This time, Bitget used 400 million dollars to test a platform's sense of responsibility in the face of a crisis. A crisis does not end a platform; responsibility can redefine a platform.
For the crypto industry, which is moving toward mainstream finance, this is also a test that must be undergone. No financial system can be built on the assumption of "never having incidents." When incidents truly occur, the tests are whether one can afford to compensate, clarify explanations, and restore operations, as these are the tests of responsibility and bottom line.
How the financial world ultimately perceives the crypto industry may depend on how it appropriately responds to a bad day.
免责声明:本文章仅代表作者个人观点,不代表本平台的立场和观点。本文章仅供信息分享,不构成对任何人的任何投资建议。用户与作者之间的任何争议,与本平台无关。如网页中刊载的文章或图片涉及侵权,请提供相关的权利证明和身份证明发送邮件到[email protected],本平台相关工作人员将会进行核查。




