Binance pledges full reimbursement after $6.3 billion security incident
Security & Exploits ·
The exchange says it has enough reserves to cover losses from a breach it describes as involving several points of entry, not one insider.
Binance co-CEO Richard Teng said the company will make whole any losses stemming from a security incident valued at roughly $6.3 billion, according to CryptoPotato. Teng pushed back on the idea that a lone staff member was responsible, describing instead a pattern of multiple entry points used by attackers to compromise the platform.
In response, Binance suspended withdrawals while it overhauls its defenses, and it is now working alongside law enforcement agencies and blockchain analytics firms to track and recover the missing assets. Roughly $3 billion of the stolen funds has already been frozen through that cooperative effort.
Separately, Binance has said it holds $6.34 billion in reserves earmarked to offset the damage, with about $5 billion of that sum sitting in the specific tokens affected by the breach, according to The Block. Industry partners account for the remaining frozen portion, bringing the total locked-down amount to around $3 billion.
To back up its reserve claims, Binance intends to publish an initial proof-of-reserves snapshot within 12 hours of its announcement, with full results expected by Monday. The exchange also said it has revoked authorizations tied to the compromised addresses as part of its immediate containment steps.
Reaction has been split. Some observers credit Binance for moving quickly and disclosing details of the breach, while others remain skeptical about the exchange's security practices and its ability to fully trace the stolen assets. That uncertainty has coincided with broader market jitters, including declines in bitcoin and ether prices.
What remains unclear is how much of the $6.3 billion will ultimately be recovered versus covered from reserves, and whether the proof-of-reserves snapshot due by Monday will satisfy lingering doubts about the scope of the multiple-breach-point attack. The timeline for restoring withdrawals has also not been specified.