Arcus: A Balance Bug Let One New Account Withdraw $2.23M, and the Company Paid It Back
A brand-new account tricked Arcus, a trading app on Robinhood Chain, into recording a huge balance and took out $2.23 million. Arcus says users lost nothing.
Key numbers
$2,234,391
Withdrawn
$3M
Blocked by rate limit
None (per Arcus)
User funds lost
1
Accounts involved
At about 10:07 on the evening of 9 November 2026, New York time, a newly created account on Arcus began asking the app to pay out money it had never put in. Before withdrawals were stopped it had pulled out $2,234,391. By the next afternoon the hole in the books was filled: Arcus said it had covered the whole shortfall from its own treasury, and that no customer balance was affected.
Arcus is a trading app built for Robinhood Chain. Robinhood is the US brokerage and crypto firm best known for its app for buying shares. Robinhood Chain is a separate payment network, an Ethereum "layer 2", meaning a faster and cheaper network that runs on top of Ethereum and settles back to it. Robinhood built it on technology from Arbitrum, another layer 2, and opened it to the public on 1 July 2026, according to The Block.
What Arcus is, and where Robinhood fits
Arcus describes itself as a self-custodial exchange: customers keep their own money in their own wallet-style accounts instead of handing it to a company, and the trading rules are enforced by smart contracts, code that moves money by itself. Spot trading began on 1 July, the day the chain launched. On 21 July the app added what The Block called 24/7 trading with no fees on more than 95 "Stock Tokens", plus a beta version of perpetual markets.
A stock token is a digital receipt that tracks the price of a real share such as Nvidia or Apple. Arcus's own legal notice says it is a contractual claim against an issuer for a cash payout, not ownership of the share itself. A perpetual, or "perp", is a bet on a price with borrowed money and no expiry date, the crypto cousin of a futures contract. Both trade around the clock, unlike a stock exchange that closes in the evening. The app settles in USDG, a stablecoin, a digital dollar issued by Paxos, with each coin meant to be worth $1.
Arcus came out of dYdX Labs, the team behind the older dYdX exchange, and is led by chief executive Eddie Zhang. Crypto Briefing reported that Robinhood Crypto, the crypto arm of Robinhood, invested in Arcus, with the amount undisclosed, and that dYdX founder Antonio Juliano sits on its board. Arcus says its product is a separate entity from the dYdX Chain. On X it describes itself as built "in partnership with" Robinhood Crypto.
That is the extent of the link. Nothing published about this incident says the fault lay with Robinhood Chain or with Robinhood itself. Arcus's report describes a flaw in Arcus's own accounting code.
What went wrong
Arcus's incident report says the problem was in how the exchange handled transfers between a user's own subaccounts. A subaccount is a separate pot inside one account, used for example to keep one trading strategy apart from another. Moving money between your own pots should simply shift it from one to the other.
Under specific conditions, Arcus said, the bug let an account record a balance "far larger than it actually held". Think of a bank ledger that let a customer move money between two of their own accounts and, through a flaw, wrote down a bigger figure at the end than they paid in. The cash in the vault has not changed, but the ledger now says the customer is rich.
The exploiter then did the ordinary thing: asked to withdraw against that balance. The system, trusting its own ledger, sent real USDG out through the bridge, the link that carries money from Robinhood Chain back to Ethereum. DefiLlama, which tracks hacks, files the case as a "withdrawal logic flaw" and describes the cause as transfers between subaccounts that inflated an account's recorded balance.
A safety brake limited the damage. The bridge has a withdrawal rate limit, a cap on how much can leave in a set period, like a cash machine that will not hand over more than a daily maximum. Arcus said it kicked in at 10:10 pm and held back a further $3 million in requests, which were never paid out and were later reversed. Arcus said only one account was involved.
The response, step by step
Arcus published a timeline in New York time:
10:10 pm: the bridge rate limit capped payouts.
10:15 pm: monitoring flagged the withdrawals and the team began investigating.
11:07 pm: withdrawals were paused for the whole platform.
11:37 pm: the fix was deployed.
11:43 pm: the exploiter's addresses were blocked from trading, transferring and withdrawing.
4:26 am on 10 November: withdrawals reopened for everyone.
5:02 am: the exploiter's pending withdrawals were reversed.
12:28 pm: the shortfall was covered from the treasury of Arcus Labs, the company behind the app.
Arcus said it detected and fixed the bug within one hour, a claim that sits a little uneasily with its own timeline, which puts the first alarm at 10:15 pm and the fix at 11:37 pm, about 80 minutes apart. Even so, the response was quick by the standards of crypto hacks, many of which run for days.
The company's post on X on 10 November said Arcus "identified and fixed a bug which permitted an unauthorized withdrawal", that no user funds were affected, and that trading and withdrawals were operating normally. The security tracker SlowMist lists the loss at $2,234,391 under the label "accounting bug". DefiLlama dates the case to 10 November, because 10:07 pm in New York is after 3 am UTC the next day. Arcus and SlowMist use 9 November.
What is still open
The money has not come back. Arcus said the withdrawn funds are being tracked on the blockchain, that it is working with blockchain investigators and will "coordinate with law enforcement as appropriate". It published the exploiter's first address and asked exchanges and other services to flag any funds that arrive from it. DefiLlama lists the full amount under "returned funds", but that appears to reflect Arcus covering the loss, not the thief handing anything back. Arcus has not reported any recovery, and no one has been named or charged.
Several questions remain unanswered. Arcus has not explained what the "specific conditions" were, how a new account found them, or why the bug was not caught before launch. It said the fix was reviewed by its security partners along with "related checks across the codebase", but did not name the firms or say whether the code had been audited before it went live. It also said it was improving its risk systems for spotting suspicious activity.
Why it matters
The size is small beside the year's big thefts: $6.34 billion from Binance in October, or $387.5 million from Bitget in September. What matters is what it shows. Arcus is one of the early apps on a chain that opened only in July, selling a very new product, share-like tokens that trade at night and weekends, which The Block says is offered in more than 120 countries. A single new account was enough to test the ledger and find a hole.
The outcome for customers depended on the company choosing to pay. Arcus's treasury covered $2.23 million this time. The rate limit is the other lesson: without it, the account could have taken roughly $5.2 million.
The aftermath
Arcus reopened withdrawals about five hours after pausing them and restored normal trading. It said it would keep tracking the withdrawn funds with blockchain investigators and would coordinate with law enforcement as appropriate, and it published the exploiter's first address. No recovery has been reported and nobody has been identified. The company has not published an outside audit, the name of its security partners or details of the flaw.
What this teaches
- A ledger bug can be as dangerous as a stolen key: if the system trusts its own recorded balance, a false number becomes real money.
- Withdrawal rate limits work as a safety brake. Here one held back $3 million that would otherwise have left.
- Customers were protected because the company chose to pay, not because the system made losses impossible. Self-custody does not remove risk from the exchange's code.
- Brand-new platforms carry untested code. Ask who has reviewed it and publish the answer.
