Robinhood Chain DEX Arcus Loses $2.23M to Accounting Bug

Robinhood Chain DEX Arcus Loses $2.23M to Accounting Bug


Arcus, a decentralized exchange operating on Robinhood Chain, disclosed that an accounting vulnerability allowed an account to withdraw approximately $2.23 million in assets on November 9, 2026. 

In an incident report published on November 10, the team said the account exploited a flaw in transfers between a user’s own subaccounts to generate an artificially inflated balance and request withdrawals against it.

Arcus team detected, paused withdrawals, fixed bug, and reimbursed $2.23 million from its treasury.

Unidentified exploiter used subaccount transfer flaw to inflate balance and withdraw $2.23 million.

Defimon Alerts (Decurity) posted an on‑chain message proposing a 90% return bounty to the exploiter.

Arcus said the incident involved one account and that no other users’ balances, positions or orders were affected. The company also said it covered the full shortfall from its treasury after pausing withdrawals and deploying a fix.

The incident gained further attention on November 11 after the automated security-alert account Defimon Alerts shared an on-chain message that purportedly came from Arcus and offered the exploiter a bounty for returning 90% of the withdrawn funds. The message’s terms include a November 13 deadline, but Arcus’s published incident report does not mention a bounty or confirm the offer.

How the Arcus Exploit Worked

According to Arcus’s incident report, the exploit began at approximately 10:07 PM Eastern Time on November 9, when a newly created account took advantage of a bug in the exchange’s handling of transfers between a user’s own subaccounts.

Under specific conditions, the flaw allowed the account to record a balance substantially larger than the assets it actually held. The account then submitted withdrawal requests against that inflated balance.

Arcus said approximately $2,234,391 in USDG was withdrawn on-chain before platform-wide withdrawals were paused. The report separately identified another $3 million in requested withdrawals that the bridge’s on-chain rate limit prevented from being paid out. Those requests were subsequently reversed. The two amounts should not be treated as a combined loss. The $2.23 million was withdrawn, while the additional $3 million was blocked before payout.

Arcus described the incident as an accounting error involving its internal subaccount system. It did not report a compromise of other users’ balances or orders, and said the issue did not affect other accounts.

Arcus Paused Withdrawals and Covered the Shortfall

Arcus’s incident report provides a timeline of its response, with all times listed in Eastern Time:

  • 10:07 PM, November 9: The first exploit activity began, according to the report.
  • 10:10 PM: The bridge’s withdrawal rate limit capped payouts and held back approximately $3 million in additional requests.
  • 10:15 PM: Arcus monitoring flagged the suspicious withdrawals, and the team began investigating.
  • 11:07 PM: The exchange paused withdrawals across the platform and updated its status page.
  • 11:37 PM: Arcus deployed a fix for the accounting bug.
  • 11:43 PM: The exploiter’s addresses were blocked from trading, transferring and withdrawing.
  • 4:26 AM, November 10: Platform-wide withdrawals were re-enabled.
  • 5:02 AM: Pending withdrawal requests from the exploiter were reversed.
  • 12:28 PM: Arcus Labs covered the shortfall using company treasury funds.

Arcus said its security partners reviewed the fix and that the team conducted additional checks across the codebase. It also said trading and withdrawals had returned to normal.

There is a timing detail worth noting. Arcus’s summary describes the bug as detected and fixed within one hour. However, its detailed timeline records monitoring at 10:15 PM and deployment of the patch at 11:37 PM, an interval of 82 minutes. The report does not explain this difference.

The treasury reimbursement means Arcus says it has covered the protocol’s shortfall; it does not mean the stolen assets have been recovered. The company said it is working with blockchain investigators to trace the withdrawn funds and will coordinate with law enforcement as appropriate.

Arcus identified the exploiter’s initial address as 0xeFbf442599310E5CeE1A4EDd5c66334c5f30b3Dd. It also asked exchanges and other service providers to flag funds received from that address.

On-Chain Message Offers a 10% Bounty

A separate development emerged through two posts from Defimon Alerts, an automated DeFi security-alert account operated by security firm Decurity. The account shared the text of an on-chain message addressed to the exploiter and described as coming from the Arcus team.

The message proposes a whitehat resolution under which the exploiter would return 90% of the withdrawn amount, approximately $2.011 million, in ETH, wrapped ETH (WETH) or DAI. The remaining 10%, approximately $223,000, would be retained as a bounty.

It identifies 0x1d4324C84e36D8104BDF327474755E5Aa0cFeBc9 as the recovery address, describing it as the Arcus Finance multisig. The message sets a deadline of November 13, 2026, at 01:00 UTC and says the sender would publicly treat the return as a whitehat recovery and not pursue further action if the funds arrive by that time.

However, the authorship of the offer remains unconfirmed. The alert’s displayed transaction metadata identifies 0x604d2124e96fdaa88b692806f8b964483328b8bb as the sending address and the exploiter’s address as the recipient. The message text separately identifies the recovery address as the Arcus multisig and says a message will also be sent from that multisig.

Why the Exploit Matters for Robinhood Chain

Arcus is one of the more prominent applications operating on Robinhood Chain. Built by the team behind dYdX, the exchange launched on the network in July 2026 and offers spot and perpetual trading. It uses a request-for-quote (RFQ) model, in which market makers compete to provide prices, rather than relying solely on a single automated market-making pool.

Robinhood launched the public mainnet of Robinhood Chain on July 1, 2026. The network is an Ethereum Layer 2 built using Arbitrum technology, according to Robinhood’s developer documentation.

Arcus’s reach has expanded alongside the chain. In an October media note, Robinhood Wallet had integrated Arcus as one of its routing providers for stock-token swaps. Arcus said at the time that it had processed more than $5 billion in cumulative spot and perpetual trading volume and attracted over 15,000 unique traders. Those figures were company-reported metrics, not independently audited user balances or assets under management.

The incident comes after other security concerns involving applications and token launches on the network. In September, an on-chain investigation linked at least $18.43 million in alleged extractions to 53 memecoin launches on Robinhood Chain. The Crypto Times covered the investigation in its report on the alleged $18.43 million Robinhood Chain memecoin operation. That episode involved token-launch activity and alleged coordinated trading, not the same type of accounting vulnerability reported by Arcus.

The distinction is important: the Arcus incident does not establish a vulnerability in Robinhood Chain itself. Arcus attributed the loss to its own subaccount accounting logic, while Robinhood’s documentation describes the network as an Arbitrum-based Layer 2. The available incident report does not identify a flaw in the chain’s underlying infrastructure.

The case also highlights how accounting and withdrawal controls can affect DeFi platforms even when users’ individual balances remain intact. In a separate incident earlier this month, The Crypto Times reported that a THORChain accounting discrepancy following an Ethereum reorganization triggered a temporary halt to swaps. The incidents had different causes, but both illustrate the importance of systems that reconcile internal balances with assets actually available for withdrawal.

What Happens Next

Arcus says the accounting bug has been fixed, the shortfall has been covered by its treasury and withdrawals have resumed. Its investigation into the withdrawn funds remains ongoing, with the company asking exchanges and service providers to flag assets linked to the exploiter’s address.

The separate whitehat message introduces another possible route to recovery, but its terms have not been confirmed by Arcus in the incident report. The November 13 deadline could become relevant if the company verifies the offer or the funds are returned.

For now, the confirmed facts are the $2.23 million unauthorized withdrawal, the additional $3 million in blocked requests, the restoration of withdrawals and Arcus Labs’ treasury reimbursement. Whether the stolen assets are recovered remains unresolved.

Also Read: Ankr Bridge Hack: $304K Drained Using Forged Cross-Chain Receipts 


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *