On October 29, an attacker moved about $6.3 billion worth of assets across 10 blockchains from Binance wallets after allegedly compromising a DevOps engineer's laptop. The breach began with 233.46 million XRP transfers and showed preparatory activity starting 36 hours earlier. Binance found no evidence of leaked wallet private keys and has pledged to cover all losses. The exchange plans to release a detailed technical report after completing its investigation.
Binance Coin (BNB) is trading at Rp12.998.683 on Pluang, down 5.64% as of Oct 30, 2026 13:01 WIB, reflecting notable market reaction following the recent Binance security breach. The platform shows a market cap of Rp1.710,11 trillion and a 24-hour trading volume of Rp80,92 trillion, with 63% of orders leaning towards selling. This trading activity highlights investor sentiment shortly after the reported $6.3 billion asset movement from compromised Binance wallets.
Following the Oct. 30 Binance hot-wallet hack, $38.8 million in Ether (ETH) was transferred from the compromised wallet to a new address, while about $1.12 billion in ETH remains in the original wallet. The partial movement suggests a wallet-to-walle...
Aethir announced on October 30 that it was not affected by the recent Binance incident. The company is conducting an audit of its systems as a precautionary measure while focusing on protecting its network and community. Aethir also commended Binance...
1inch quickly blocked addresses tied to a Binance attack across its decentralized app, wallet, and API, working with partners to update the blocklist within an hour. However, the stolen 1INCH tokens cannot be frozen because the token lacks freeze and...
After a theft involving Binance, 1inch quickly blocked addresses linked to the stolen assets from its decentralized app, wallet, and API within an hour. However, because 1INCH tokens follow the ERC-20 standard without freeze or blacklist functions, t...
Blockchain investigator ZachXBT revealed that stolen funds from Binance ($6.3B) and Bitget ($388M) attacks passed through THORChain before being mixed at the same address. This on-chain connection suggests the possibility that both incidents involved...
