{"id":117,"date":"2026-11-01T12:02:01","date_gmt":"2026-11-01T09:02:01","guid":{"rendered":"https:\/\/makersgroup.online\/blog\/?p=117"},"modified":"2026-11-01T12:02:01","modified_gmt":"2026-11-01T09:02:01","slug":"binance-says-it-replenished-90-of-assets-after-6-3-billion-hack","status":"publish","type":"post","link":"https:\/\/makersgroup.online\/blog\/binance-says-it-replenished-90-of-assets-after-6-3-billion-hack\/","title":{"rendered":"Binance Says It Replenished 90% of Assets After $6.3 Billion Hack"},"content":{"rendered":"<p><strong>On October 31, 2026, Binance said it had covered about 90% of the assets affected by the hack and that users would not bear the financial loss. This describes replenishment of affected customer assets using exchange resources and related funds; it does not, by itself, show that Binance recovered 90% of the stolen tokens.<\/strong><\/p>\n<h2>What did Binance say about replenishing affected assets?<\/h2>\n<p><strong>Binance said it had raised coverage of the affected losses to about 90%, up from roughly 80% in its previous update.<\/strong><\/p>\n<p>In an update dated October 31, 2026, Binance said it had covered about 90% of the amount affected by the incident. The exchange also said BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC were fully backed at 100%.<\/p>\n<p>These are figures and statements published by Binance. They should be described as the company\u2019s replenishment and backing claims, not as an independent audit of every balance.<\/p>\n<h2>Does this mean Binance recovered 90% of the stolen crypto?<\/h2>\n<p><strong>No. Replenishing affected balances and recovering tokens taken by attackers are different things.<\/strong><\/p>\n<p>The coverage claim describes how the exchange is restoring affected assets for customer balances. It does not establish how much of the stolen crypto was seized from the attackers or returned to the platform.<\/p>\n<p>So a headline saying \u201cBinance recovered 90% of the crypto\u201d would go beyond the confirmed information. A more precise description is that Binance said it had replenished or covered about 90% of the affected amount.<\/p>\n<h2>What funds does Binance say it is using?<\/h2>\n<p><strong>Binance named corporate funds, a partial deployment of SAFU and funds from its Futures Insurance Fund.<\/strong><\/p>\n<p>Binance\u2019s update listed several sources for replenishing assets: corporate funds, a partial deployment of the Secure Asset Fund for Users (SAFU), and funds from the Futures Insurance Fund. The company said it\u2014not users\u2014would bear the financial impact of the loss.<\/p>\n<p>Those disclosures describe the sources Binance says it is using; they are not a complete independent accounting of every asset movement. Public reports put the incident\u2019s estimated impact at about $6.3 billion.<\/p>\n<h2>What remains unclear after the update?<\/h2>\n<p><strong>The 90% announcement does not independently verify full restoration of balances or the return of stolen tokens.<\/strong><\/p>\n<p>The available coverage reports Binance\u2019s statement and the funding sources it named, but does not provide an independent audit of every figure. The 90% figure also cannot be taken to mean that the same share of stolen assets has been seized from the attackers.<\/p>\n<p>It helps to separate three questions: how much was affected, how much Binance says it has covered for customer assets, and how much of the stolen crypto was actually recovered. This update primarily addresses the second question.<\/p>\n<h2>FAQ<\/h2>\n<h3>When did Binance announce that it had replenished 90% of affected assets?<\/h3>\n<p>In an update published on October 31, 2026.<\/p>\n<h3>Were 90% of the stolen tokens recovered?<\/h3>\n<p>The available statement concerns replenishing or covering affected assets. It does not confirm that 90% of the tokens were recovered from the attackers.<\/p>\n<h3>Which funding sources did Binance name?<\/h3>\n<p>The exchange cited corporate funds, a partial deployment of SAFU and funds from its Futures Insurance Fund.<\/p>\n<h3>Who did Binance say would bear the financial loss?<\/h3>\n<p>Binance said the exchange would bear the financial impact rather than users. This is the company\u2019s stated position.<\/p>\n<h2>Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.binance.com\/en-GB\/support\/announcement\/security-incident-recovery-update-3-90-of-stolen-assets-replenished-proof-of-reserves-snapshot-provided-2026-10-31-1fdf1f61559c401da0435895ffcccb62\" target=\"_blank\" rel=\"noopener noreferrer\">www.binance.com<\/a><\/li>\n<li><a href=\"https:\/\/www.coindesk.com\/business\/2026\/10\/31\/binance-says-it-has-replaced-90-of-stolen-crypto-after-massive-usd6-3-billion-breach\" target=\"_blank\" rel=\"noopener noreferrer\">www.coindesk.com<\/a><\/li>\n<li><a href=\"https:\/\/apnews.com\/article\/883f18140c1e21ce0c38781e72cbe315\" target=\"_blank\" rel=\"noopener noreferrer\">apnews.com<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>On October 31, 2026, Binance said it had covered about 90% of the assets affected by the hack. That is a replenishment claim\u2014not proof that 90% of the stolen tokens were recovered.<\/p>\n","protected":false},"author":1,"featured_media":115,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[93],"tags":[118,70,57,117,116],"class_list":["post-117","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-crypto-exchanges-institutional-infrastructure-regulation","tag-asset-replenishment","tag-binance","tag-crypto-exchange-security","tag-exchange-breach","tag-safu"],"_links":{"self":[{"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/posts\/117","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/comments?post=117"}],"version-history":[{"count":1,"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/posts\/117\/revisions"}],"predecessor-version":[{"id":119,"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/posts\/117\/revisions\/119"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/media\/115"}],"wp:attachment":[{"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/media?parent=117"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/categories?post=117"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/makersgroup.online\/blog\/wp-json\/wp\/v2\/tags?post=117"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}