mt logoMyToken
ETH Gas
简体中文

Binance Hacker Moves Another 78,400 ETH and Swaps to BTC for Money Laundering, Involving About US$142 Million

According to PANews, funds tied to the Binance hacker have seen another large transfer, with 78,400 ETH moved out and swapped cross-chain into BTC for money laundering, involving approximately US$142 million. The incident was characterized as a major security incident in the source material. The biggest change in this move is that the asset form shifted from ETH to BTC, and the tracking path is no longer limited to records on a single chain. As of now, public information has not disclosed the specific wallet addresses, transaction hashes, timing of operations, cross-chain tools, or exchange platforms, and details of the incident remain subject to subsequent public on-chain information. Therefore, what can currently be confirmed is the scale of the transfer, the direction of the swap, and the amount basis, while execution details still need to be supplemented.

Based on the confirmed data, the entity involved is funds related to the Binance hacker; the actions include another transfer and a cross-chain swap; and the quantitative core is 78,400 ETH and approximately US$142 million in involved funds. The source material's basis for judgment is that the amount involved is large and the funds were swapped cross-chain into BTC for money laundering, on which basis it considers the incident to have high market attention and tracking value. It should be noted that the source material provides both the asset quantity and the US dollar amount, but does not disclose the conversion time point or pricing method. The US dollar value of crypto assets fluctuates with price, so the US$142 million should be regarded as the amount basis given by the source material, rather than an exact price that can be simply back-calculated. This basis does not affect the characterization of the incident, but it is relevant for accurately citing the data. The available material also does not provide address clusters, transaction timing, swap ratios, the final location of the funds, or responses from relevant parties; confirmed facts are concentrated on the asset quantity, swap direction, and amount basis. In terms of characterization, the classification as a major security incident comes from the source material and does not mean that legal or attribution-level determinations have been completed.

The cross-chain swap is the core step in this fund transfer. As background, unlike ordinary transfers that remain on the original chain, a cross-chain swap changes the chain and accounting environment in which the asset sits, moving funds from the ETH system into the BTC system; tracking therefore requires establishing cross-chain data links among the outflow, swap, and receipt stages. The source material's emphasis on "cross-chain swap" and "swap into BTC" already indicates that the fund flow is not a one-way on-chain transfer but involves a conversion of asset form; for on-chain analysis and anti-money laundering monitoring, this path increases identification complexity. It should be made clear, however, that the above explanation of cross-chain operations and tracking complexity is general background analysis and not a specific path confirmed by the source material. The source material does not give the name of a specific cross-chain bridge or platform, nor does it state whether the swap was completed in one transaction, and relevant judgments remain subject to subsequent public on-chain records. From this perspective, the cross-chain swap is both a channel for fund flows and an important node for on-chain tracking and risk identification; current information is still insufficient to reconstruct the swap process.

From the perspective of security incident handling, large involved funds moving from ETH to BTC means that follow-up attention cannot remain only on the original asset but must also cover the destination of the assets after the swap. If hacker-related funds change their form through asset conversion and cross-chain operations, this may both delay identification and require label data and transaction data on different chains to correspond. The key points usually discussed in such incidents include whether fund flows can be continuously identified, whether relevant addresses will be flagged, and whether the swap stage leaves on-chain records that can be tracked. These discussions belong to the incident tracking level and do not constitute a judgment on market prices or funding conditions. It should be noted that before specific address labels and cross-chain paths are available, relevant discussions should be based on currently disclosed facts, and general anti-money laundering analysis should not be packaged as conclusions already confirmed by the source material.

In terms of the completeness of the material, current public information is mainly concentrated at the headline and summary level and does not yet cover the full fund transfer chain. Known content includes 78,400 ETH, the cross-chain swap into BTC, approximately US$142 million in involved funds, and the characterization of money laundering and a major security incident; unknown content is concentrated on the specific transaction timing, address labels, cross-chain path, swap ratio, final location of the funds, and responses from relevant parties. For financial news, these information gaps directly affect judgment of the full picture of the incident. Follow-up attention may be paid to whether public information supplements transaction hashes and address labels, whether it discloses the specific platform or tool used in the swap stage, and whether new fund transfer actions emerge. Only after these facts are confirmed can the fund path be more fully reconstructed. The core facts that can be confirmed at present are: funds related to the Binance hacker have again moved 78,400 ETH and swapped them cross-chain into BTC for money laundering, involving approximately US$142 million, and the incident is classified by the source material as a major security incident. For market participants, it is more important to continuously track confirmed facts than to make advance judgments on the outcome of the incident when information is insufficient. The report is sourced from PANews; if new on-chain transfers or statements from relevant parties emerge later, they can serve as a basis for further verifying the progress of the incident. In terms of reporting scope, the original material is relatively brief, so this article only elaborates on disclosed elements and does not infer undisclosed addresses or paths.

免责声明:本文版权归原作者所有,不代表MyToken(www.mytokencap.com)观点和立场;如有关于内容、版权等问题,请与我们联系。
更多精彩内容请查阅
X(https://x.com/MyTokencap)
或加入社区了解更多MyToken-官方华文电报群
(https://t.me/mytoken_cn)