Independent record. Not associated with, endorsed by or operated by Binance. This site is read-only: there is nothing to sign in to, pay for or connect.
An independent record of the October 2026 Binance hack
Statements
Each statement is one attributed line with a verbatim quote from a stored copy of the source. Only approved statements are shown.
Official means the party said it, not that it is true.
Verified on-chain. Reproduced by us from raw chain data kept in our own storage. The method is shown.
Official. Stated by the party concerned (an exchange, an agency, a token issuer or similar), attributed to them. Official means the party said it, not that it is true.
Reported. Stated by news media or an analytics firm, attributed to them.
Disputed. Credible sources conflict. The statement links the sources that disagree.
Debunked. Contradicted by primary evidence, which is linked.
Theory. Speculation, attributed to whoever proposed it, shown with the evidence for and against.
Binance has now covered approximately 95% of the impacted amount, up from 90% in our prior update. The outstanding 5% are tokens outside the top ten listed above, and are less liquid in the market and take longer time to source at the required scale.
The US Secret Service said on Friday it is "working around the clock" with private sector partners "to identify, freeze, trace, and recover funds" stolen from Binance.
Binance has consistently pledged to cover 100% of the losses from what is suspected to be crypto's biggest hack on record and said it has set aside more than $6.34bn in company funds to do so.
Our last update explained that Binance had set aside more than $6.34B in company funds to cover hacked losses, and we had already covered approximately 80% of the impacted amount of the hacked loss at that time. That covered amount is now up to 90%.
The replenishment employed: - A partial deployment of the Secure Asset Fund for Users (SAFU). This is expected to happen over the next 24 hours; users can view the updated balance here. - A portion of our Futures insurance fund. The remaining balance of the Futures insurance fund is a regulatory requirement. Users can check the updated balance of the fund here. - Binance's own corporate treasury.
The firm has also been tracking funds stolen in Binance’s separate multibillion-dollar hack, saying the attackers are using automation to obscure the trail and leveraging DeFi protocols on Tron to dodge stablecoin freezes.
frozen funds don’t necessarily equate to recovered funds. Immobilizing assets prevents the suspected attackers from spending them, but it doesn’t automatically return them to Binance or its users.
We have already set aside more than $6.34B in company funds, with $5B held in the exact impacted token assets that were stolen, such as USDC, USDT, BTC, ETH, BNB, etc. This means that we have already covered approximately 80% of the impacted amount.
Binance has said it will cover all losses using its SAFU fund and company funds, and that it has reserved more than $6.34 billion of company funds to do so. Around $5 billion of this is already held in the same tokens that were stolen, and Binance is buying the rest through the market and OTC trades. It plans to publish a full Proof of Reserves report by Monday.
Binance has set aside more than $6.34 billion in company funds to cover losses from the hack, the exchange said. The company said $5 billion of those funds were already held in the same tokens affected by the attack.
Binance has pledged to meet customer losses through its SAFU reserve and company resources, announcing more than $6.34bn of company funds separate from roughly $3bn of frozen assets.
The Secret Service said that its investigators "are working around the clock with our private-sector partners, including Circle, to identify, freeze, trace and recover funds stolen from Binance on Thursday."