Cc9f267dcClaimDuring the October 29 Binance hack, the attacker pre-signed 50 transactions with differing nonces to execute a transaction on the Binance hot walletAgreeDisagree
Cc9f267dcClaimFollowing the October 29 Binance hack, automated scripts distributed funds from the original 10 attacker wallets across over 100 new addresses, then fan-out split them across more than 400 addressesAgreeDisagree
Cc9f267dcClaimOn Thursday, October 29, at approximately 4:00 PM Eastern Time, Binance suffered a hack that drained approximately $6.3 billion to $6.4 billion in assetsAgreeDisagree
Cc9f267dcClaimThe attacker behind the October 29 Binance hack borrowed approximately 20,000 Ether against collateral on the Aave lending protocolAgreeDisagree
Cc9f267dcClaimAccording to Chainalysis data, North Korea-linked operations accounted for 15% of total reported cryptocurrency hack losses in 2021AgreeDisagree
Cc9f267dcClaimThe October 29 Binance hack transferred over $6 billion in cryptocurrency within a 20-minute windowAgreeDisagree
Cc9f267dcClaimThe multi-chain withdrawals during the October 29 Binance hack compromised Binance's internal transaction signing infrastructure rather than leaking the underlying private keysAgreeDisagree
Cc9f267dcClaimFollowing the October 29 Binance hack, the Aave community voted to freeze Aave lending markets across all networks to prevent the attacker from swapping or borrowing against stolen collateralAgreeDisagree
Cc9f267dcClaimFollowing the October 29 Binance hack, asset issuers and protocols including Circle, Tether, and the Arbitrum Security Council froze approximately $3 billion of the stolen fundsAgreeDisagree
Cc9f267dcClaimBinance's initial public investigation into its October 29, 2026 hack stated that a compromised DevOps engineer's laptop allowed an attacker to access a service container and execute unauthorized withdrawal transactionsAgreeDisagree
Cc9f267dcClaimAccording to Chainalysis data, suspected North Korea-linked cyber operations accounted for nearly 89% of all reported cryptocurrency hack losses in 2026AgreeDisagree
Cc9f267dcClaimFollowing the October 29 Binance hack, the Federal Bureau of Investigation, the United States Secret Service, and the Internal Revenue Service Criminal Investigation unit publicly requested THORChain node operators to block TraderTraitor addressesAgreeDisagree
Cc9f267dcClaimOn the Saturday following the October 29, 2026 Binance hack, THORChain node operators halted trading across multiple chains after an Ethereum block reorg caused THORChain to pay out 10 Ether that its vault had not receivedAgreeDisagree
Cc9f267dcClaimDuring the October 29 Binance hack, the attacker used Ethereum Improvement Proposal 7702 to convert the Binance Ethereum hot wallet into an account controlled by an external smart contractAgreeDisagree
Cc9f267dcClaimThe Ethereum Improvement Proposal 7702 smart contract upgrade allowed the attacker to automatically sweep incoming customer deposits directly out of the Binance hot wallet during the October 29 Binance hackAgreeDisagree
Cc9f267dcClaimThe October 29 Binance hack drained assets held across Binance hot wallets on Ethereum, Bitcoin, Tron, and SolanaAgreeDisagree
Cc9f267dcClaimDuring the laundering of the October 29 Binance hack proceeds, the attacker sold approximately $60 million worth of Tether to market makersAgreeDisagree
Cc9f267dcClaimAccording to Chainalysis data, the average loss per suspected North Korea-linked cryptocurrency hack rose from $50 million in 2021 to $185 million in 2026AgreeDisagree
Cc9f267dcClaimDuring the October 29, 2026 Binance hack, assets were drained from Binance hot wallets across XRP, Ethereum, Arbitrum, Avalanche, Optimism, Base, Tron, Solana, and Polygon networksAgreeDisagree
Cc9f267dcClaimThe THORChain solvency checker triggered an emergency pause halting Ethereum transaction signing within two minutes of detecting a vault shortfallAgreeDisagree