BNB Chain confirmed that its networks and bridges remain fully operational following a security incident at Binance involving unauthorized withdrawals estimated at $6.3 billion.
On October 30, 2026, one day after the breach at the exchange, BNB Chain released a statement affirming that its infrastructure and core networks remained intact. The chain specified that BNB Smart Chain (BSC), opBNB, BNB Greenfield, and its cross-chain bridges were all fully operational and that funds held on-chain were safe.
Scope of the Binance Incident
The breach at Binance involved unauthorized withdrawals that primarily affected the exchange's hot wallets. Binance pledged to cover the losses by drawing on its Secure Asset Fund for Users (SAFU) and corporate reserves.
Approximately $3 billion in stolen assets has been frozen through work with blockchain partners and issuers. Analytics firms TRM Labs and Chainalysis linked the breach to TraderTraitor, a group with connections to North Korea. The attackers reportedly gained their initial access through a compromised laptop belonging to a DevOps engineer.
The Distinction Between Exchange and Blockchain
BNB Chain's statement underscored an important distinction: cryptocurrency held in an exchange account differs from cryptocurrency held in a user's own wallet on a blockchain. While Binance and BNB Chain share historical ties and branding, BNB Chain is a separate network infrastructure from the exchange's operations.
BNB Smart Chain serves as the main network, opBNB functions as a scaling layer, and BNB Greenfield focuses on data storage. The cross-chain bridges connecting BNB Chain to other blockchains were specifically called out as operational.
What Comes Next
Key developments to monitor include when Binance resumes withdrawals and details on new safeguards, whether the $3 billion in frozen assets grows or decreases, and the continued normal operation of BNB Chain's networks. For users holding assets directly on BNB Chain rather than on the exchange, the statement indicates their funds were not affected by the breach.
