Binance set aside $5 billion of its own funds to make users whole after the hack and arranged with partners to buy $1.34 billion more, covering the $6.34 billion stolen

Overview Debates Related claims Topics Sources

Cc9f267dcNews eventClaim

The Bank of Russia granted self-regulatory status to the NAUFOR for digital financial asset and crypto platform operators

Cc9f267dcNews eventClaim

Cryptocurrency exchange KuCoin announced the immediate termination of all products, services, and features for users in Russia and Belarus

Cc9f267dcNews eventClaim

Cryptocurrency exchange MEXC announced its withdrawal from serving users in Russia and Belarus

Cc9f267dcClaim

LlamaRisk reported on October 30, 2026, that the Aave position of the hacker behind the $6.3 billion Binance exploit remained overcollateralized with $59.9 million in assets against $43.8 million in debt

Cc9f267dcClaim

KuCoin stated that affected customers in Russia and Belarus will receive notifications detailing deadlines and instructions to close positions and withdraw assets, while unnotified accounts require no action

Cc9f267dcClaim

During Aave's freeze triggered by the Binance hack starting October 29, 2026, blocked deposits and ongoing supplier withdrawals drove utilization in major stablecoin pools to 92–100%

Cc9f267dcClaim

A Bitget cryptocurrency exploit in September 2026 resulted in a loss of $387 million

Cc9f267dcClaim

Elliptic reported that attackers divided 18,270 stolen Bitcoin from the Binance hack on October 29, 2026 across 19 addresses, holding approximately 1,000 BTC in most addresses

Cc9f267dcClaim

Chainalysis reported on October 30, 2026, that attackers in the $6.3 billion Binance hack on October 29, 2026 used automated wallet loops and dense transaction networks across hundreds of interconnected addresses to circulate stolen assets

Cc9f267dcClaim

Aave set a zero loan-to-value ratio on V3 and zero collateral factor on V4 for nine assets including USDT, USDC, USDT0, POL, WAVAX, sAVAX, XAUt, PAXG, and OP, following the Binance hack

Cc9f267dcClaim

Attackers in the Binance breach on October 29, 2026 converted approximately 434 million USDT into 160,451 ETH on Uniswap, 1inch, and request-for-quote systems at prices 12% to 26% worse than market rates, according to Elliptic

Cc9f267dcClaim

KuCoin did not publicly disclose the specific sanctions measures behind its decision to exit Russia and Belarus, the number of affected user accounts, or the total trading volume involved in its exit

Cc9f267dcClaim

Elliptic reported that attackers in the Binance hack on October 29, 2026 converted approximately $786 million in stolen stablecoins into Ethereum and Tron before asset freezes took effect

Cc9f267dcClaim

Investigators identified a laundering pattern on the Tron blockchain where numerous wallets received exactly 1 TRX before receiving and forwarding additional funds in the $6.3 billion Binance breach on October 29, 2026

Cc9f267dcClaim

Attackers in the Binance breach on October 29, 2026 exchanged approximately 234 million USDT for 638 million TRX on SunSwap and sold $48 million in RLUSD stablecoins alongside approximately 150 other stolen tokens, according to Elliptic

Cc9f267dcClaim

As of October 30, 2026, none of the 18,270 stolen Bitcoin divided across 19 addresses in the Binance hack on October 29, 2026 had reached an identified exchange or trading service, according to Elliptic

Cc9f267dcClaim

Aave's zero collateral restrictions imposed after the $6.3 billion Binance hack prevent restricted assets from backing new loans while allowing existing V3 positions to retain their health scores and liquidation thresholds

Cc9f267dcClaim

The Binance cryptocurrency platform suffered a major cyberattack on October 29, 2026, resulting in estimated losses between $6.3 billion and $6.4 billion

Cc9f267dcClaim

LlamaRisk reduced Slope2 borrowing-rate parameters on Aave to flatten the upper interest-rate curve and protect borrowers from escalating rates during deposits blocked by the Binance hack

Cc9f267dcClaim

The Bank of Russia granted self-regulatory status to the NAUFOR for digital financial asset and crypto platform operators

Cryptocurrency exchange KuCoin announced the immediate termination of all products, services, and features for users in Russia and Belarus

Cryptocurrency exchange MEXC announced its withdrawal from serving users in Russia and Belarus

LlamaRisk reported on October 30, 2026, that the Aave position of the hacker behind the $6.3 billion Binance exploit remained overcollateralized with $59.9 million in assets against $43.8 million in debt

KuCoin stated that affected customers in Russia and Belarus will receive notifications detailing deadlines and instructions to close positions and withdraw assets, while unnotified accounts require no action

During Aave's freeze triggered by the Binance hack starting October 29, 2026, blocked deposits and ongoing supplier withdrawals drove utilization in major stablecoin pools to 92–100%

A Bitget cryptocurrency exploit in September 2026 resulted in a loss of $387 million

Elliptic reported that attackers divided 18,270 stolen Bitcoin from the Binance hack on October 29, 2026 across 19 addresses, holding approximately 1,000 BTC in most addresses

Chainalysis reported on October 30, 2026, that attackers in the $6.3 billion Binance hack on October 29, 2026 used automated wallet loops and dense transaction networks across hundreds of interconnected addresses to circulate stolen assets

Aave set a zero loan-to-value ratio on V3 and zero collateral factor on V4 for nine assets including USDT, USDC, USDT0, POL, WAVAX, sAVAX, XAUt, PAXG, and OP, following the Binance hack

Attackers in the Binance breach on October 29, 2026 converted approximately 434 million USDT into 160,451 ETH on Uniswap, 1inch, and request-for-quote systems at prices 12% to 26% worse than market rates, according to Elliptic

KuCoin did not publicly disclose the specific sanctions measures behind its decision to exit Russia and Belarus, the number of affected user accounts, or the total trading volume involved in its exit

Elliptic reported that attackers in the Binance hack on October 29, 2026 converted approximately $786 million in stolen stablecoins into Ethereum and Tron before asset freezes took effect

Investigators identified a laundering pattern on the Tron blockchain where numerous wallets received exactly 1 TRX before receiving and forwarding additional funds in the $6.3 billion Binance breach on October 29, 2026

Attackers in the Binance breach on October 29, 2026 exchanged approximately 234 million USDT for 638 million TRX on SunSwap and sold $48 million in RLUSD stablecoins alongside approximately 150 other stolen tokens, according to Elliptic

As of October 30, 2026, none of the 18,270 stolen Bitcoin divided across 19 addresses in the Binance hack on October 29, 2026 had reached an identified exchange or trading service, according to Elliptic

Aave's zero collateral restrictions imposed after the $6.3 billion Binance hack prevent restricted assets from backing new loans while allowing existing V3 positions to retain their health scores and liquidation thresholds

The Binance cryptocurrency platform suffered a major cyberattack on October 29, 2026, resulting in estimated losses between $6.3 billion and $6.4 billion

LlamaRisk reduced Slope2 borrowing-rate parameters on Aave to flatten the upper interest-rate curve and protect borrowers from escalating rates during deposits blocked by the Binance hack

Binance promised to cover user losses from the Binance hack using its SAFU reserve and corporate funds, according to its October 30, 2026 statement