mt logoMyToken
ETH Gas
EN

Bitget Hacker Laundered $161M in BTC in 11 Days, Funds Mainly Routed to Mixers

A hacker linked to Bitget laundered about $161 million in BTC over 11 days, with the funds mainly flowing into mixers, PANews reported.

According to PANews, new developments have emerged in the major exchange security incident involving Bitget: the hacker involved laundered approximately $161 million in BTC over 11 days, with the funds mainly flowing into mixers. The incident is classified as the aftermath of a major exchange security incident and has drawn market attention due to the large amount involved and the BTC money-laundering path, giving it notable security-warning value. The core facts center on three aspects: the laundering period, the scale of the assets involved, and the main direction of fund flows. Public information has not disclosed further details about specific addresses, transaction batches, or handling results.

In terms of nature, this is an exchange security incident that has entered the follow-up handling stage. Public information does not provide the hacker's identity, the specific time of the attack, or the platform's compensation arrangements, but it clearly points the focus to the fund-laundering stage. The 11-day window indicates that the funds were not transferred all at once but were continuously processed over a relatively short period. The $161 million BTC scale places the incident in the high-value range, and the asset form being Bitcoin means the fund flows are directly related to Bitcoin's on-chain path. The funds mainly flowing into mixers indicates that the laundering process used channels that may affect the identification of fund flows. Together, these three elements form the basis of current market attention.

On the time dimension, 11 days is a noteworthy observation window. The hacker completed the laundering of a large amount of BTC in a relatively short period, turning the incident from a static result after a security attack or theft into an ongoing fund-transfer process. For exchange security incidents, whether follow-up funds can be identified, frozen, or traced in a timely manner often directly affects the degree of risk spillover. Market attention is no longer limited to the incident itself but extends to the pace of on-chain handling of the BTC involved. The 11-day span also provides a clear reference for observing platform response, on-chain tracking, and fund-interception efficiency.

On the amount and asset level, $161 million places the incident in the high-value range. As one of the core assets in the crypto market, Bitcoin's on-chain path is traceable, but the involvement of mixers significantly increases identification difficulty. The flow to mixers is one of the most indicative details in this incident: the funds did not remain in a single account or a simple transfer chain that can be intuitively identified, but entered more complex flow links. For on-chain analysis, inflows to mixers mean that tracing work must seek new identification clues amid changes in fund paths; for exchanges and compliance teams, this path increases the difficulty of identifying subsequent intersections of the funds. Public information only provides the directional fact of 'mainly flowing into' and does not specify the mixer's name, the proportion used, or whether all funds have completed laundering. Therefore, it is impossible to conclude from available information whether the funds have completely left the traceable range or have entered other asset forms.

The reason the market is focused on the large-scale BTC laundering is that the information covers three dimensions at once: scale, asset, and time. $161 million is a large amount, BTC is a core crypto asset, and 11 days means the laundering activity continued over a relatively short period. The combination means the incident is no longer a static security notice but a fund-handling case that can be continuously observed. For readers, the core fact is that the hacker has conducted large-scale laundering of the BTC involved, with the funds mainly flowing to mixers. For the industry, the incremental information this fact provides is that the follow-up stage of an exchange security incident may also affect the market's assessment of risk-control capabilities. Due to the lack of more on-chain details, market attention currently remains at the factual level and is not yet sufficient to form a complete judgment of the full picture.

From the perspective of industry security warnings, the value of this incident lies in its follow-up nature. Exchange security depends not only on defenses at the time of the incident but also on post-incident fund monitoring, risk isolation, and information disclosure. The hacker laundered a large amount of BTC within 11 days and mainly routed it to mixers, making fund handling a key link in the incident's impact chain. Although available information does not disclose Bitget's specific response measures, the incident itself has prompted the market to focus on the platform's ability to identify abnormal fund flows and the transparency of follow-up management of security incidents. Relevant discussion should be based on disclosed facts and avoid turning amount and flow information into unverified judgments of responsibility.

At the industry level, market assessments of exchange risk control often include post-event links. Defensive capability at the time of attack is only one part; whether funds can be quickly located after the incident, clear statements issued, and collaboration with on-chain analysis firms carried out also affects the effectiveness of risk handling. In the current incident, the hacker completed large-scale laundering within 11 days and the funds mainly flowed into mixers, indicating that the timeliness of follow-up handling is particularly critical. However, available information does not disclose the platform's specific timeline, so outsiders cannot yet judge its response speed, nor can the fact of fund laundering be directly equated with inadequate platform handling.

In terms of information completeness, the currently confirmable elements include: the entity involved is a Bitget-related hacker incident; the laundering period is 11 days; the amount involved is approximately $161 million; the asset is BTC; the funds mainly flowed into mixers; and the incident is the aftermath of a major exchange security incident. Elements not disclosed in public information include the hacker's identity, the specific attack time, on-chain addresses, the tranching of funds, law-enforcement involvement, the platform's compensation arrangements, and the mixer's name and usage proportion. These undisclosed matters prevent outsiders from judging whether the funds have completely left the traceable range, the effectiveness of the platform's handling, and the full picture of the incident.

Follow-up matters worth watching include: whether further disclosure of fund flows emerges, whether mixer-related paths continue to be tracked, whether trading platforms and regulators publish handling progress, and whether the industry strengthens follow-up management of security incidents on this basis. The above observation points are all bounded by available information and do not constitute judgments on prices or platform operations. Overall, the incident has extended from a single-platform security event to on-chain fund tracing, exchange risk handling, and industry security warnings. Its subsequent developments still depend on disclosure of fund flows, progress in on-chain tracking, and further statements from the platform and regulators. The judgment supported by current information is limited to the fact that the incident has entered the stage of fund laundering and flow handling; more disclosure is still needed to assess the full risk picture.

Disclaimer: This article is copyrighted by the original author and does not represent MyToken’s views and positions. If you have any questions regarding content or copyright, please contact us.(www.mytokencap.com)contact
More exciting content is available on
X(https://x.com/MyTokencap)
or join the community to learn more:MyToken-English Telegram Group
(https://t.me/mytokenGroup)