Reserve

Change

Uniswap

SAFU

Token

<h2 id="span-span-style-font-size-16px-what-happened-in-the-binance-rsr-exploit-span-span">What Happened in the Binance RSR Exploit?</h2>
<a href="https://www.coingabbar.com/en/binance-hacked-news-today-biggest-crypto-heist-bnb-reaction" rel="noopener noreferrer nofollow">The Binance RSR</a> Exploit ended with 3.38 billion RSR sold in about 15 minutes. The attacker swapped the full amount for 1,856 ETH, worth roughly $4.1M, on Uniswap v3.
<img alt="Reserve Post on X" src="https://d3iuzwoiyg9qa8.cloudfront.net/webadmin/storage/public/commonEditerImage/787Cq3C0y7ItZwXaM2dFhhWLlh93TpstSr7r1xn1.png" width="300" height="441" title="Reserve Post on X">
Source:<a href="https://x.com/reserveprotocol/status/2115945656791466457?s=20" style="background-color: rgb(255, 255, 255)" rel="noopener noreferrer nofollow">Reserve Post on X</a>
The team first flagged a suspected Binance hot wallet exploit involving about 3.4B RSR. A later update put the figure at 3.38 billion RSR stolen. It described the event as an exchange custody incident, not a flaw in the token or its contracts.
<h2 id="span-span-style-font-size-16px-how-fast-did-the-3-38b-rsr-dump-hit-uniswap-span-span">How Fast Did the 3.38B RSR Dump Hit Uniswap?</h2>
The swaps ran between 8:53 and 9:08 PM ET on October 29, which is 00:53 to 01:08 UTC on October 30. The&nbsp;<a href="https://etherscan.io/token/0x320623b8E4fF03373931769A31Fc52A4E78B5d70?a=0xB58Bf76D209Fa71F60013CE1933CA331177a4F08#transactions" rel="noopener noreferrer nofollow">onchain transaction record</a> shows the wallet activity behind the RSR Uniswap Sale.
<img alt="Onchain transaction record " src="https://d3iuzwoiyg9qa8.cloudfront.net/webadmin/storage/public/commonEditerImage/Q3EqF6InXbVZHbCa146MkHXWiFRH6yFd3HdFSgxn.png" width="300" height="630" title="Onchain transaction record ">
The reported figures imply an average exit price near $0.0012 per RSR. That is a simple calculation from $4.1M and 3.38B tokens, not an official price.
<img alt="Onchain transaction record " src="https://d3iuzwoiyg9qa8.cloudfront.net/webadmin/storage/public/commonEditerImage/XQW5hCWcWon5P6viHtYSJfjtCSdX94hCNwRuZ9wI.png" width="300" height="583" title="Onchain transaction record ">
The RSR Token Sell-Off came in one burst. No official assessment has been published of the RSR Price Impact.
<h2 id="span-span-style-font-size-16px-who-bought-the-stolen-rsr-after-the-sell-off-span-span">Who Bought the Stolen RSR After the Sell-Off?</h2>
The protocol team says arbitrage bots and other traders bought the tokens. No individual buyer has been named, so the final holders of the 3.38B RSR Dump remain unknown.
The team also highlighted that some swaps&nbsp;could include wash trades through hidden wallets funded by the attacker. That means the on-chain picture may still change.
As far as Reserve can see, the attacker no longer holds any RSR. This reportedly rules out using the tokens in bulk against Reserve DTF governance.
<h2 id="span-span-style-font-size-16px-did-the-reserve-liquidity-withdrawal-protect-rsr-token-security-span-span">Did the Reserve Liquidity Withdrawal Protect RSR Token Security?</h2>
Before the sale, The project withdrew its treasury-provided on-chain liquidity so it could not become the attacker’s exit.&nbsp;
This Reserve Liquidity Withdrawal left other pools and traders to take the other side of the sale. Third-party LPs in RSR pools were also advised to consider doing the same.
RSR is immutable with no admin keys, so nobody, including Reserve, <a href="https://www.coingabbar.com/en/paxg-freeze-paxos-locks-1906-tokens-after-binance-incident" rel="noopener noreferrer nofollow">can freeze it</a>. That limits what RSR token security measures can do after a theft.
<img alt="The team update on X" src="https://d3iuzwoiyg9qa8.cloudfront.net/webadmin/storage/public/commonEditerImage/oZAMtNUn3GIMYvrwRxKXSJIUzzUhFK9jQdSd54mB.png" width="300" height="496" title="The team update on X">
In its&nbsp;<a href="https://x.com/reserveprotocol/status/2116034504078807234?s=20" style="background-color: rgb(255, 255, 255)" rel="noopener noreferrer nofollow">Reserve Protocol update</a>, the team said its contracts were not affected and holders need not act. It sees no reason to pause any product and is watching for knock-on effects.
<h2 id="span-span-style-font-size-16px-will-the-binance-safu-fund-cover-the-loss-span-span">Will the Binance SAFU Fund Cover the Loss?</h2>
Binance said it will cover all losses from the&nbsp;<a href="https://x.com/binance/status/2115993361517891592" rel="noopener noreferrer nofollow">Binance SAFU Fund</a> and company funds, that user funds are safe, and that it will publish an updated Proof of Reserves after remediation.
The team interprets this as an intention to buy back the lost assets, including 3.38B RSR. It added that Binance has not briefed it on the details and that it has not analyzed Binance’s ability to absorb the loss.
The posts reviewed do not explain how the <a href="https://www.coingabbar.com/en/binance-hack-2026-6-3-billion-impact-crypto-losses" rel="noopener noreferrer nofollow">Binance Security</a> Breach happened.
<h2 id="span-span-style-font-size-16px-expert-take-what-could-change-after-the-binance-rsr-hack-span-span">Expert Take: What Could Change After the Binance RSR Hack?</h2>
The data suggests the sale is complete on-chain and that Reserve’s contracts were untouched. The main uncertainty is how Binance replaces the 3.38B RSR, since the team has not received details about the recovery method.
Key signals include the updated proof of reserves, any new large RSR transfers, and order book depth on exchanges. The unresolved points are the attack route, the wash trade possibility, and the full RSR price impact.
<h2 id="span-span-style-font-size-16px-conclusion-span-span">Conclusion</h2>
The <a href="https://www.coingabbar.com/en/binance-security-incident-6-3-billion-impact-laptop-attack" rel="noopener noreferrer nofollow">Binance security incident</a> moved a large block of RSR into the market within minutes. The team reports no damage to its protocol, and Binance says it will absorb the loss. The identity of the buyers and the repurchase method are still open.
Further RSR Crypto News and Reserve Protocol News will depend on Binance’s remediation update. Daily&nbsp;<a href="https://www.coingabbar.com/en/crypto-news-english" rel="noopener noreferrer nofollow">crypto news today</a> coverage tracks cryptocurrency news and the latest crypto news as new details appear.
Disclaimer: This article is for information only and is not financial or investment advice. Crypto assets are volatile and carry risk, and details of this incident may change as new information emerges.

Binance RSR Exploit: Who Bought 3.38B Tokens After the $4.1M Dump?

Table of Contents

Coingabbar

Other articles published on Oct 30, 2026

Join our free newsletter for daily crypto updates!