Binance Hackers Use CoinJoin for First Time, $2.85B Funds Frozen
Key Highlights
- Elliptic identified the first documented use of CoinJoin involving funds stolen in the October 29 Binance breach, with mixing activity beginning on November 1.
- Approximately 28 BTC, worth around $2.2 million, passed through 18 separate CoinJoin transactions by 06:02 UTC on November 2.
- Of the approximately $6.43 billion stolen, $2.85 billion has been frozen or seized, while around $3.24 billion remains in addresses linked to the theft.
Blockchain analytics firm Elliptic reported that the group responsible for stealing approximately $6.43 billion from Binance has used CoinJoin for the first time to mix a portion of the stolen Bitcoin.
Of the total amount stolen, $2.85 billion, or 44%, has been frozen or seized. Around $3.24 billion remains in addresses linked to the theft.
According to Elliptic’s report, CoinJoin activity has become a significant part of the attackers’ recent fund movements. The mixing began on November 1 and continued into the following day, marking the first documented use of the technique involving funds from this incident.
By approximately 05:00 UTC on November 1, transfers on the Tron network had largely stopped. The distribution wallet completed its final transfer at 05:33 UTC, following 1,113 transfers over 51 hours.
Beginning at 05:55 UTC that day, Bitcoin derived from the Tron-related funds entered CoinJoin transactions using the WabiSabi protocol.
Later on November 1, some of the ETH held in reserve was swapped for Bitcoin, with most of the resulting Bitcoin also directed into the same CoinJoin process.
By 06:02 UTC on November 2, approximately 28 BTC, valued at $2.2 million, had passed through 18 separate CoinJoin transactions.
What is CoinJoin?
CoinJoin is a transaction method that combines Bitcoin belonging to multiple users into a single transaction. By mixing inputs and outputs, it makes it more difficult to establish direct on-chain links between the coins entering the transaction and those leaving it.
Wallets such as Wasabi Wallet use the WabiSabi protocol to coordinate these transactions. Elliptic identified the November 1 and November 2 activity as the first instance of funds stolen in the Binance incident being processed through CoinJoin.
Parallel movements across other blockchains
While the CoinJoin activity was underway, funds on other networks were also moving.
Beginning at 07:00 UTC on November 1, NEAR tokens were transferred to new accounts. At 08:19 UTC, portions of the ETH held in reserve began moving again in batches of approximately 10 ETH.
At 09:38 UTC, roughly half of the SOL was transferred to a new address, with smaller amounts subsequently moved out. NEAR has not moved since.
Early on November 2, the stolen XRP moved for the first time since the original theft. Between 02:12 and 04:00 UTC, all 233 million XRP was transferred to six new addresses, where it remains.
On Solana, some SOL was swapped for USDC and then back into SOL. The funds were also routed through a lending vault, with deposits made from one address and withdrawals sent to another.
Techniques used alongside CoinJoin
Elliptic described a combination of techniques used to complicate the tracking of stolen funds.
The attackers split funds across thousands of new addresses and moved assets between blockchains through at least seven bridges. This separated deposits from payouts across different networks.
Tokens were also swapped on decentralized exchanges, changing the assets being tracked. Funds were routed through lending vaults, making it more difficult to establish direct links between sending and receiving addresses.
Bitcoin was mixed through CoinJoin transactions.
Approximately $16 million has also been sent to addresses that hold proceeds from the September 2026 Bitget exploit.
Current location of the funds
The report further reveals that of the $6.43 billion stolen, $2.85 billion is frozen. Approximately $3.24 billion remains in addresses linked to the theft. Most of the remaining sum has not yet been mixed or converted and is held primarily in Bitcoin and ETH across the nine largest addresses.
Only a negligible amount appears to have been cashed out. The majority of observed activity has involved conversion between assets while the funds stay on public blockchains in addresses connected to the original theft.
Elliptic stated that the overall process has involved 11 blockchains, around 12,000 wallets, and more than 40,000 transactions. Tron served as a major distribution route, with funds spread across about 7,700 addresses.
Background on the October 29 incident
According to Elliptic, the theft began at approximately 20:05 UTC on October 29, when five Binance wallets on the XRP Ledger transferred 233 million XRP to a single attacker-controlled address.
The incident was also described in The Crypto Times’ Binance hack explainer.
Over the following 30 minutes, Binance hot wallets on Solana, NEAR, Base, Optimism, Bitcoin, Tron, Ethereum, Arbitrum, and Avalanche were also drained. A second wave of withdrawals targeted Binance wallets on Avalanche and Polygon shortly after 23:00 UTC.
The largest losses occurred on Ethereum, totaling $3.80 billion across 186 tokens, including 1.9 billion USDT and 823 million USDC, according to the report.
The attacker also took 18,270 BTC, then valued at $1.48 billion, and 612.7 million USDT on Tron.
Four assets accounted for 74% of the total losses: USDT on Ethereum, BTC, USDC, and USDT on Tron. Two-thirds of the Ethereum losses, amounting to $2.53 billion, were transferred in a single transaction at 20:24 UTC.
Binance paused withdrawals and stated that it would cover customer losses using its SAFU fund and company reserves. The exchange set aside more than $6.34 billion for that purpose.
On November 1 at 06:00 UTC, Binance announced it had begun reopening withdrawals, starting with the Bitcoin network.
Binance’s investigation indicated the incident may have involved a compromised DevOps engineer’s laptop that allowed access to a service container and the submission of unauthorized withdrawal transactions. Later statements described the attack as complex and noted additional points of breach. The attacker employed a self-destruct mechanism that removed tooling and traces during the operation.
Also Read: Binance Completes zk-SNARK Proof for 10 Tokens After $6.3B Hack
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


