AI-assisted summary, reviewed by NullTX editors.
On-chain data indicates the attacker behind the $6.3 billion Binance theft depositing about $4 million into three Binance deposit addresses.
According to recent reports, at the same time, Binance's first post-hack reserve snapshot reveals its biggest assets covered with buffers as small as 2.7 ETH and $6 of USDT. Binance's full zero-knowledge proof of those figures is due by Tuesday.
Some of the money stolen from Binance has started going back to Binance.
Blockchain intelligence firm Arkham has flagged the entity it tracks as "Binance Hacker" depositing about $4 million into three Binance deposit addresses. Arkham says those addresses "likely represent nested service(s)." These are third-party exchanges that use Binance for liquidity and custody, giving their own customers deposit addresses that sit on Binance's infrastructure.
Sources indicate that if Arkham is right, the hacker isn't depositing into an ordinary Binance account. The money would be going to smaller platforms that operate through Binance. Exchanges have long known this is a weak point for stolen funds moving into normal trading. Either way, Binance is now receiving stolen funds at its own deposit addresses while it works to show customers it has replaced what was taken.
The FBI has attributed the October 29 theft to North Korea. The deposits come at a sensitive moment. Binance has just published its first reserve snapshot since the hack and has promised a full cryptographic proof of it by Tuesday.
$4 million is a small slice of a theft worth about $6.3 billion, but it matters for two reasons.
Recent findings suggest that it shows how the laundering works. Nested services are a common way into the regulated financial system. A third-party platform that relies on Binance for custody may run weaker identity checks on its own people. Funds deposited there can be swapped and withdrawn without the hacker ever opening a Binance account.
Industry observers note that binance can act on it. Binance can't freeze bitcoin and ether sitting in wallets nobody controls, and it doesn't control the stablecoins that issuers like Tether and Circle have frozen. Deposits that land at its own addresses are different: they are on Binance's platform, so Binance can freeze them itself. One of the first tests of how Binance handles the money still in the hacker's hands is whether it freezes these funds and identifies the services that own the addresses.
While the hacker's funds move, Binance has been rebuilding its reserves. Its proof-of-reserves page now shows:.
Industry observers note that the first page covers Binance's six largest assets. Customer balances are what users hold. Reserves are on-chain wallet balances, including assets held with outside custodians.
The second page has four more assets, and two of them stand out:.
Sources indicate that why USD1 and RLUSD matter: these are two of the stablecoins whose issuers froze stolen funds after the attack. World Liberty Financial froze $27 million of USD1, and Ripple began freezing RLUSD the same night. Both now show reserves above what Binance owes customers.
Assets with outside custodians: part of several reserves sits with outside custodians rather than in Binance's own exchange wallets:.
Asset | Held with third-party custodians.
Sources indicate that the striking part isn't that the ratios reach 100%. It's how closely they stop there.
Compared with October's report: Binance's previous monthly report, published in early October before the hack, showed BTC at 100.35% and USDT at 103.88%. ETH was already at exactly 100.00%. After the theft:.
It has been revealed that not every asset is that tight. USDC, ZEC and BNB carry buffers of 1.3% to 6%. The thinnest buffers are in BTC, ETH, USDT and SOL, which are among the assets the attacker took in the largest amounts.
In a recent development, how Binance indicates it got here: the pattern fits Binance's account of replacing the stolen assets in stages. It reported 80% replaced on Friday, 90% on Saturday and 95% on Sunday. The remaining 5% is in less-liquid tokens it is still buying. The money came from:.
Binance confirmed taking 7,499 BTC from SAFU and has pledged to refill the fund to about $1 billion.
What the snapshot can't show: it was taken a little over a day after the theft, once the rebuild was under way. It indicates the balance sheet after the replacement, not how large the gap was on October 29.
According to recent reports, binance says the full proof takes 40 to 50 hours to compute. Its latest patch says it will be ready "by Tuesday, 2026-11-03 (UTC)." The system is open source, in Binance's zkmerkle-proof-of-solvency repository.
What the proof guarantees, according to the project's circuit design document:.
Sources indicate that the design also guards against a "dummy user attack" identified by Ethereum Foundation researcher Enrico Bottazzi. In that attack, fake accounts holding cheap tokens are used to offset debts in major assets.
In a recent development, what it doesn't prove: the reserve side. The project's verifier config describes the totals as information "published by CEX, it represents CEX's liability." The reserve figures are checked a different way, against the wallet addresses Binance publishes through the page's "Download All Address" option.
Recent findings suggest that what customers can do: each user can get a Merkle proof for their account and check it against the published root. They can use the verifier code in Binance's repository rather than Binance's own interface. That doesn't prove Binance is solvent, but it confirms the user's balance was counted.
It has been revealed that binance has rebuilt its reserves to 100% across its ten largest assets, but on several of them the buffer is only a few coins. Meanwhile, stolen funds are reaching its deposit addresses through platforms that run on its infrastructure. Tuesday's proof can confirm customer balances. It can't show how Binance handles the stolen money arriving at its own door.
Disclosure: This is not trading or investment advice. Always do your research before buying any cryptocurrency or investing in any services. Follow us on X @nulltxnews.
In a recent development, paying a Bittensor subnet with gamma burns its alpha token. Here is how gamma gets minted, how the lower-price rule works and why the credit can never be converted back.Pay a Bittensor subnet for an AI answer with gamma, and your payment vanishes. The alpha token behind it gets burned, the credit gets spent, and nobody can redeem either one.One Wallet Replac….
It has been revealed that finCEN's November 6 order cuts US financial institutions off from MEXC Global, barring any transmittal of funds to or from the exchange. The order spells out what is banned, what MEXC is accused of, and how the exchange has answered.MEXC claims user assets remain secure. The FinCEN order never suggested otherwise, and the gap between the exchange's reassurance….
Industry observers note that zetaChain's Governance Proposal 2 would halt its L1 around Dec 9, mint ZETA 1:1 on Solana and burn about 55M ZETA in monthly installments. Voting closes Nov 7.Headlines are calling it a 55 million ZETA burn. Read the proposal's own schedule, though, and nothing close to 55 million disappears on the day the chain halts. The figure is real, but it arrives in t….
In a recent development, eZAR opened its rand-pegged token to the public on November 2 with R303 million in circulation. Its reserve yield is the feature that puts the stablecoin label to the test.Most stablecoin rolls out promise a token that never moves. eZAR's disclosures say its holders can make money or lose it. The rand-pegged token went live to the public on November 2, and it….
One email a week with our upcoming explainers and the news behind them.
More explainers and analysis from NullTX.
