Arcus, the decentralized exchange for perpetuals and tokenized stocks that runs on Robinhood Chain, lost 2,234,391 USDG on the night of November 9-10, 2026. No one stole a private key or forced a smart contract: a newly created account got the system to credit it with a larger balance than it had deposited and withdrew against it. The platform suspended withdrawals at 23:07 Eastern Time and reopened them at 04:26 on the 10th with the flaw already fixed.
The origin of the hole matters more than its size. The money did not come from another user's wallet but from an off-chain ledger that Arcus keeps and that authorizes payments against what that ledger states. The Arcus Labs treasury covered 100% of the shortfall, so no customer lost balance, although the company has not said it has recovered a single dollar of what was withdrawn. What failed here was not a lock, it was a subtraction.
The other three million the attacker tried to move afterwards never made it out, halted by withdrawal caps. That is 2.23 million against the 605 that DeFi lost in twenty days of April 2026, according to this outlet's loss tally.
The sequence of one night
The report Arcus published after the incident places the exploit on the night of the 9th and attributes it to a newly opened account. The attacker did not need to access anyone's wallet: it was enough to move funds between two of its own subaccounts and take advantage of the fact that the system, under certain conditions, recorded a balance far higher than the amount transferred. Against that invented balance, withdrawals went through without friction.
Withdrawals were suspended at 23:07 Eastern Time on November 9, and the team took about thirty minutes to fix the vulnerability. Reopening came at 04:26 on November 10, after reviewing the code with external security partners. Arcus also blocked the attacker's addresses from trading, transferring and withdrawing, and asked exchanges to flag any funds leaving them, a gesture that serves to hinder an escape rather than to return the money.
The report rules out collateral damage: a single affected account, with no changes to the balances, positions or orders of other clients. The money, however, had already left the system by the time the team reacted.
An inflated balance in a ledger that lives off-chain
Arcus is not a run-of-the-mill DEX. The technical documentation describes it as an exchange built by dYdX Labs to trade tokenized stocks and perpetuals, with an order engine that matches off-chain, its own validators that re-verify every block, and custody and final settlement on Robinhood Chain, an Ethereum layer 2.
On that architecture, each account is identified by a pair: the wallet address and a subaccount index from 0 to 9. Each index holds its own collateral and its own request limits, and internal movements between indices of the same wallet are signed with the wallet itself. The documentation says it plainly: those internal transfers are never settled on-chain, the money moves between indices inside the exchange.
There lies the crack. If the internal movement does not touch the chain, the balance that authorizes a withdrawal is calculated by Arcus's code, and a calculation error becomes a payment permit. The money that leaves afterwards is real: the withdrawal crosses the bridge and settles against the collateral held in custody on Robinhood Chain. The flaw was in the arithmetic, not in the signatures.
The cap that prevented the loss from doubling
On the second attempt, the system would not let it through. A withdrawal limit stopped about three million dollars more and the funds were reversed, so the confirmed loss stayed at 2.23 million and not 5.23. Arcus documents its capstwo million USDG per transaction and eight million per day at the protocol level, plus the limits imposed by the bridge's liquidity for each destination chain.
That cap is the difference between an incident and an operational collapse, and it worked where audits do not reach. It is the kind of control that nobody boasts about on the blog and that decides the final bill on a bad day.
| Concept |
Amount |
Status |
| Withdrawn by the attacker |
2,234,391 USDG |
Confirmed loss |
| Withdrawals blocked |
~3,000,000 USDG |
Reverted to the system |
| Covered by the treasury |
2,234,391 USDG |
Assumed by Arcus Labs |
| 90% refund offer |
~2,011,000 USDG |
Pending until November 13 |
| Reward offered (10%) |
~223,000 USDG |
Conditional on return of funds |
The coverage came from Arcus Labs' treasury, which absorbed the entire shortfall with its own funds. Covering is not recovering: the company's balance sheet is left with a 2.23 million hole and the attacker keeps the liquidity unless they agree to return it. For the customer, the difference between the two is decisive, because their balance never moved.
On November 11 a message appeared on the chain addressed to the attacker's address. It offered the usual deal: return 90% of the amount, about $2,011,000 in ETH, WETH or DAI to a recovery address before November 13 at 01:00 UTC, and keep the remaining 10%, about 223,000, as a reward. If the money came back in time, Arcus would treat the episode as a white-hat rescue of 90%.
The fine print is that the company's official report does not mention that offer, and the press attributes it to security alert accounts that circulated the message. An on-chain message is a unilateral proposal: no one can force the recipient to accept it and the white-hat classification is decided afterwards by the company. Treating the rescue as settled before the deadline is reading wishful thinking as fact.
The deadline expires at 01:00 UTC on November 13. Until then, the only verifiable facts are that the message exists, that the figures match the loss and that the clock is running for both parties.
The pattern shared by this year's scares
Arcus's mistake looks less like a heist and more like a chain of oversights. This month, ACryptoS lost $665,000 across 77 vaults due to an input validation flaw, offered the same 10% to the attacker and shut down the project. In May, Stake DAO saw 5.4 trillion fake vsdCRV minted on Arbitrum before anyone could stop it. Neither case required a private key.
The pattern has a structural explanation. Hybrid exchanges, with an off-chain order book and on-chain custody, move the attack surface from the contract to the accounting, and accounting is not audited with the same discipline as Solidity. A miscalculated balance breaks no signature and triggers no contract alert: it only produces a number the system believes and pays out on.
When the income statement is written by a balance
The practical lesson fits in one sentence that is uncomfortable for the sector. Withdrawal caps, so unglamorous, did more to limit the damage than any prior audit: Arcus survived the flaw because a three million withdrawal did not fit within the limit and because its treasury had 2.23 million available to plug the gap without asking anyone's permission.
It remains to be seen whether the attacker accepts the deal before November 13 and whether Arcus publishes the outcome with the same detail with which it published the diagnosis. While the clock runs, the case leaves a question that every DEX with sub-accounts should answer in writing: who checks, and how often, that the sum of internal balances still matches what is on the chain.