<h2 id="span-style-font-size-16px-color-inherit-font-weight-bolder-binance-security-incident-last-2-span-span-style-font-size-16px-color-inherit-font-weight-bolder-span-span-style-font-size-16px-color-inherit-font-weight-bolder-span-span-style-font-size-16px-color-inherit-font-weight-bolder-still-missing-bnb-at-717-span">Binance Security Incident: Last 2% Still Missing, BNB at $717</h2>
As of November 5, 2026, crypto news today brings a new <a href="https://www.coingabbar.com/en/relay-protocol-binance-hack-transaction-delays-explained" rel="noopener noreferrer nofollow">Binance hack update</a>: the exchange says about 98% of the impacted amount is now replenished.&nbsp;
Per its<a href="https://x.com/binance/status/2118001921252347938" rel="noopener noreferrer nofollow">official X post</a> dated November 4, 2026, the Binance security incident recovery now hinges on the final 2%. BNB trades near $717.34 on CoinGecko.
<h2 id="span-span-style-font-size-16px-binance-security-incident-update-today-what-changed-span-span">Binance Security Incident Update Today: What Changed?</h2>
The exchange’s handle also covered this news in its tweet on X, shown below.<img alt="Binance security Incident update 7" src="https://d3iuzwoiyg9qa8.cloudfront.net/webadmin/storage/public/commonEditerImage/F9RxPnBqFVVI1BpUZ1gOthiiJFH2zmxsxq37HpeZ.png" width="300" height="786" title="Binance security Incident update 7">
<ul>
 <li style="margin-left: 0px; list-style-type: disc">More than 100% of the needed funds is set aside from company resources.</li>
 <li style="margin-left: 0px; list-style-type: disc">Replenishment reached about 98% of the impacted amount.</li>
 <li style="margin-left: 0px; list-style-type: disc">Remaining tokens are bought through market and OTC channels.</li>
 <li style="margin-left: 0px; list-style-type: disc">Withdrawals reopen in phases while safeguards are strengthened.</li>
</ul>
The post also promises further updates as progress continues.
<h2 id="span-span-style-font-size-16px-binance-98-replenished-how-did-coverage-climb-span-span">Binance 98% Replenished: How Did Coverage Climb?</h2>
<div>
 <table>
 <colgroup>
 <col width="389">
 <col width="214">
 </colgroup>
 <tbody>
 <tr>
 <td>Update</td>
 <td>Coverage</td>
 </tr>
 <tr>
 <td>Earlier update</td>
 <td>About 80%</td>
 </tr>
 <tr>
 <td>Prior update cited in Recovery Update #4</td>
 <td>About 90%</td>
 </tr>
 <tr>
 <td>November 4 update</td>
 <td>About 98%</td>
 </tr>
 </tbody>
 </table>
</div>
The stolen funds replenished so far leave 2% open. Those are low-liquidity tokens, so buying them will be slower, and the exchange expects the pace to lag.&nbsp;
Binance stolen funds still outstanding are small, yet they decide when the exchange hack recovery ends.
<h2 id="span-span-style-font-size-16px-binance-proof-of-reserves-44-tokens-snapshot-what-is-new-span-span">Binance Proof of Reserves 44 Tokens Snapshot: What Is New?</h2>
<div>
 <table>
 <colgroup>
 <col width="258">
 <col width="351">
 </colgroup>
 <tbody>
 <tr>
 <td>Item</td>
 <td>Detail</td>
 </tr>
 <tr>
 <td>Snapshot time</td>
 <td>2026-11-04 00:00 UTC</td>
 </tr>
 <tr>
 <td>Tokens covered</td>
 <td>44 (previously 10)</td>
 </tr>
 <tr>
 <td>Proof generation</td>
 <td>About 50 to 60 hours</td>
 </tr>
 </tbody>
 </table>
</div>
Binance PoR 44 tokens widens the check, giving an updated view of assets that are fully accounted for.&nbsp;
After the zero-knowledge proof finishes, holders can confirm balances are at least 1:1 backed on the<a href="https://www.binance.com/en/proof-of-reserves" rel="noopener noreferrer nofollow">Proof of Reserves (PoR) website</a>.
<h2 id="span-span-style-font-size-16px-binance-hack-6-3-billion-how-much-was-stolen-span-span">Binance Hack $6.3 Billion: How Much Was Stolen?</h2>
On October 30, the exchange said it had<a href="https://x.com/binance/status/2116121748555153621" rel="noopener noreferrer nofollow">reserved over $6.34 billion</a> of company funds, with $5 billion already held in the affected tokens.&nbsp;
The November 4 post adds that more than 100% of the required amount is now set aside.
<h2 id="span-span-style-font-size-16px-binance-safu-fund-hack-coverage-who-pays-span-span">Binance SAFU Fund Hack Coverage: Who Pays?</h2>
The PoR page describes <a href="https://www.coingabbar.com/en/crypto-currency-news/binance-safu-fund-bitcoin-strategy-strengthens-user-protection" rel="noopener noreferrer nofollow">the SAFU fund</a> as an emergency reserve for hacks. The November 4 post, however, says the company, not users, bears the cost.
<h2 id="span-span-style-font-size-16px-do-binance-withdrawals-resume-fully-yet-span-span">Do Binance Withdrawals Resume Fully Yet?</h2>
Recovery Update #4 set phase one for 06:00 to 09:00 UTC on November 1. Phased withdrawals continue, and no full reopening date appears in the November 4 post.
<h2 id="span-span-style-font-size-16px-bnb-price-after-binance-security-incident-key-numbers-span-span">BNB Price After Binance Security Incident: Key Numbers</h2>
<a href="https://www.coingecko.com/en/coins/bnb" rel="noopener noreferrer nofollow">Data from CoinGecko</a>, as of November 5, 2026, shows BNB price today at:
<div>
 <table>
 <colgroup>
 <col width="220">
 <col width="352">
 </colgroup>
 <tbody>
 <tr>
 <td>Metric</td>
 <td>Value</td>
 </tr>
 <tr>
 <td>Price</td>
 <td>$717.34</td>
 </tr>
 <tr>
 <td>7d change</td>
 <td>-4.2%</td>
 </tr>
 <tr>
 <td>24h range</td>
 <td>$681.40 to $722.78</td>
 </tr>
 <tr>
 <td>Market cap</td>
 <td>$94.379B</td>
 </tr>
 </tbody>
 </table>
</div>
<img alt="BNB Token Price today" src="https://d3iuzwoiyg9qa8.cloudfront.net/webadmin/storage/public/commonEditerImage/wVuFSi67v72aZzMZv2D5vL9pq2WogdVvDdT5KHaF.jpg" width="300" height="730" title="BNB Token Price today">
Neither CoinGecko nor the exchange ties this move to the hack.
<h2 id="span-span-style-font-size-16px-is-binance-safe-is-my-money-safe-on-binance-after-hack-span-span">Is Binance Safe? Is My Money Safe on Binance After Hack?</h2>
The exchange keeps saying user funds safe, backed by its own reserves. The pending proof will test that claim, because it lets users verify balances themselves.&nbsp;
Are Binance funds safe is therefore a question the proof, not a post, should answer.
<h2 id="span-span-style-font-size-16px-expert-view-what-could-come-next-span-span">Expert View: What Could Come Next?</h2>
Analysts following <a href="https://www.coingabbar.com/en/binance-hack-fbi-north-korea-stolen-ethereum-update" rel="noopener noreferrer nofollow">Binance hack news</a> today may treat the final 2% and the proof output as two tests.&nbsp;
The <a href="https://www.coingabbar.com/en/binance-security-incident-news-today-fake-interview-bnb-price" rel="noopener noreferrer nofollow">Binance security incident</a> could stay open until the exchange publishes its post-incident report.&nbsp;
Liquidity in the remaining tokens may decide how fast the last 2% closes. Price impact remains uncertain. Readers of <a href="https://www.coingabbar.com/en/crypto-news-english" rel="noopener noreferrer nofollow">crypto news</a> should watch both.
Disclaimer: This article is for information only and is not financial, legal, or investment advice. Crypto assets are volatile, and you can lose money. Verify details with official sources before making any decision.

Binance Security Incident: One Gap Still Open, BNB Price Today?

Table of Contents

Coingabbar

Other articles published on Nov 5, 2026

Join our free newsletter for daily crypto updates!