Binance’s $6.3B hack leaves questions over hot wallet safeguards

Binance’s $6.3B hack leaves questions over hot wallet safeguards

Binance’s $6.3B Hack Leaves Questions over Hot Wallet Safeguards

Experts say blockchain records show repeated wallet drains but cannot establish Binance’s internal signing controls or transaction limits. Binance’s $6.3 billion security incident has left unanswered questions about how the exchange managed its hot wallets and limited the amount attackers could access.

Binance co-CEO Richard Teng stated on October 30th that the attack affected the exchange’s own hot wallet. Most customer assets were held in offline cold storage and moved to hot wallets only upon user withdrawal requests.

Wallet balances provide a partial view of an exchange’s exposure to an attack. Public blockchain records can indicate funds moving, yet they do not confirm the internal controls governing those transfers, as explained by CertiK analyst Jonathan Riss in an interview with Cointelegraph.

In its initial report on Tuesday, Binance disclosed that attackers accessed an internal wallet-signing service to transfer funds outside the normal withdrawal process. The exchange decided to keep some technical details confidential to prevent further attacks.

The exchange did not respond to Cointelegraph’s inquiries regarding its wallet balances and safety measures.

Rivals such as Coinbase, Gate, and Upbit have revealed their cold storage ratios following the attack.

What Blockchain Records Can Reveal

Riss noted that the $6.3 billion figure represented the cumulative value of affected assets across ten blockchains. On Ethereum, attackers repeatedly drained a hot wallet as new deposits arrived.

When attackers obtain valid signatures, their potential access depends on the permissions granted by the signing system. A wallet’s balance at a single moment does not reveal the full scope of their exposure.

Riss further explained that transaction limits enforced by the application requesting a signature can be bypassed if that application is compromised. However, limits set independently by the signing system may still restrict transfers.

“Comparing Binance’s safeguards with other exchanges is challenging from an external perspective,” Riss added. “Public information on internal signing architecture is limited everywhere, and reserve distribution and proof-of-reserves attestations show the location of assets, not the withdrawal authorization process.”

Eugene Hahr, BitGo’s chief product officer, declined to speculate on Binance’s internal safeguards, stating, “The breakdown of custody arrangements is a question Binance is best placed to answer.”

How Much Should Exchanges Keep in Hot Wallets?

Idan Ofrat, co-founder and chief product officer at Fireblocks, mentioned that exchanges typically maintain enough funds in hot wallets to cover a few days’ worth of expected withdrawals, often representing a low single-digit percentage of assets under management.

Exchanges generally store the majority of customer assets in cold storage, while some utilize intermediate wallets that require manual approval for transfers to hot wallets.

Alex Tobol, chief technology officer at Telegram-based crypto wallet Walt, noted that holding billions of dollars in hot wallets is not uncommon for an exchange of Binance’s size. Hot wallets typically process withdrawals automatically, but replenishing them from cold storage should require a separate treasury decision and manual approval.

Hahr emphasized that controls applied before signing, including transaction limits, approved withdrawal addresses, and additional authorization requirements, can help contain losses when a system is compromised.

Cointelegraph reported that Binance hackers raced to move billions before it could be frozen.

Leave a Reply