Arcus Exploit, November 2026: What Happened to the $2.2M and What Users Should Check
Table of Contents
On the night of November 9, 2026 (US Eastern time), a single newly created Arcus account used an accounting bug to withdraw 2,234,391 USDG it was not entitled to. Arcus paused withdrawals, deployed a fix, and says it covered the full shortfall from the Arcus Labs treasury. It also says no other user's balance, position or order was affected.

Source: Arcus, "Arcus Incident Report: November 9, 2026", captured November 17, 2026, used under fair use for educational purposes.
ArcusGuide is an independent site with no connection to Arcus, dYdX or Robinhood, and nothing here is financial advice. This page sticks to what Arcus and named outlets have published, and says so where they disagree or stay silent.
What happened
Arcus's report says that at around 10:07 PM ET on November 9, a newly created account "exploited a bug in how the exchange handled transfers between a user's own subaccounts." Under specific conditions, the bug let the account record a balance far larger than it actually held, and the account then requested withdrawals against that inflated balance.
Some context on sub-accounts: Arcus runs its perps on Robinhood Chain, and its developer docs say one wallet can hold up to 10 of them, each with its own collateral balance, and that funds can move between them inside the same wallet. That internal transfer is where the bug sat.
| Time (ET) | What happened | Source |
|---|---|---|
| Nov 9, ~10:07 PM | New account starts exploiting the sub-account transfer bug | Arcus report |
| Nov 9, 10:10 PM | Bridge rate limit caps payouts and holds back $3M of further requests | Arcus report |
| Nov 9, 10:15 PM | Arcus monitoring flags the withdrawals; team starts investigating | Arcus report |
| Nov 9, 11:07 PM | Platform-wide withdrawals paused; status page updated | Arcus report |
| Nov 9, 11:11 PM | Status page incident "Perps withdrawals are paused" opens (04:11 UTC Nov 10) | status.arcus.xyz |
| Nov 9, 11:37 PM | Bug fix deployed | Arcus report |
| Nov 9, 11:43 PM | Exploiter's addresses blocked from trading, transferring and withdrawing | Arcus report |
| Nov 10, 4:26 AM | Platform-wide withdrawals re-enabled | Arcus report |
| Nov 10, 5:02 AM | Exploiter's pending withdrawals reversed | Arcus report |
| Nov 10, 12:28 PM | Shortfall covered from the Arcus Labs company treasury | Arcus report |
| Nov 11 | Crypto Times reports an on-chain bounty message attributed to Arcus | Crypto Times |
| Nov 13 | Crypto Briefing reports CertiK's integer-underflow finding | Crypto Briefing |
The report's summary says Arcus "detected and fixed the bug within one hour." Its own timeline puts monitoring at 10:15 PM and the fix at 11:37 PM, which is 82 minutes. Crypto Times pointed out the same gap, and Arcus has not explained it.
On the cause, Arcus calls it an accounting bug and gives no code-level detail. Crypto Briefing reported on November 13 that the security firm CertiK attributes the incident to an integer underflow, a math error where a number that should go below zero wraps around to a very large positive value, and that CertiK traced nine payouts from the bridge contract. Arcus has not confirmed or disputed that description.
What Arcus has said about user funds
Arcus's report makes four statements about money, all in its own words:
- $2,234,391 USDG was withdrawn on-chain before withdrawals were stopped.
- A further $3M of requested withdrawals was held by the bridge's on-chain rate limit, "never paid out, and later reversed." That $3M is not part of the loss, and Crypto Times also warns against adding the two figures together.
- "No other user balances, positions, or orders were affected," and only a single account was involved.
- "The temporary shortfall has been fully covered by Arcus Labs from the company's treasury."
Arcus also says its security partners reviewed the fix along with related checks across the codebase, and that it is working with blockchain investigators and "will coordinate with law enforcement as appropriate." It published the exploiter's initial address, 0xeFbf442599310E5CeE1A4EDd5c66334c5f30b3Dd, and asked exchanges and service providers to flag funds received from it.
Covered is not the same as recovered
How to check your own account
Arcus says only one account was involved. If you want to see your own numbers for yourself, these checks read what the interface and the chain show. None of them asks you to move funds.
Open the app from a bookmark
Go to app.arcus.xyz directly, not through a link in a DM, reply or search ad. Incidents bring out fake "claim" and "refund" pages.
Look at your balances
The Portfolio page (app.arcus.xyz/portfolio) shows your Spot and Perps balances. Compare them with what you expect from your own deposits, trades and funding.
Check open positions and orders
Arcus says no positions or orders were affected. Your open positions and resting orders should match what you placed.
Review withdrawals
Perps withdrawals move funds to your Spot balance first, and a Spot withdrawal then bridges out. Any withdrawal you made should appear on both legs, and none you did not make should appear at all.
Cross-check on-chain
Paste your wallet address into the Robinhood Chain explorer at robinhoodchain.blockscout.com to see its token transfers independently of the Arcus interface.
If something does not match, contact Arcus through the chat on help.arcus.xyz or at support@arcus.xyz, the address its incident report gives for questions. Withdrawals that failed or were slow between 11:07 PM and 4:26 AM ET on November 9 to 10 fall inside the pause window; Arcus's withdrawal guide covers the normal flow.
What is still unknown
- Whether any of the money comes back. Arcus says the funds are "being tracked on-chain." It has published nothing on recovery since.
- The bounty. Crypto Times reported on November 11 that Defimon Alerts, an automated alert account run by the security firm Decurity, shared an on-chain message described as coming from the Arcus team. Per that report, the message offered the exploiter 10% (about $223,000) to return 90% (about $2.011M) by November 13 at 01:00 UTC. Arcus's incident report does not mention a bounty, and Arcus has not said whether the deadline passed with any return.
- The technical detail. Beyond "accounting bug" in sub-account transfers, Arcus has not published a code-level post-mortem. The integer-underflow description comes from CertiK via Crypto Briefing.
- The one-hour claim. The summary and the timeline disagree by about 22 minutes, as noted above.
- Which code was audited. The published third-party audits of Arcus cover its rootchain contracts. The What Is Arcus explainer lists what was reviewed. Arcus has not said which of its partners reviewed this fix.
How to tell official Arcus updates from scams
Exploits pull in phishers fast. Expect fake "Arcus refund," "compensation claim" and "recovery" pages, plus DMs from people posing as Arcus staff or investigators. Arcus's report announces no claim process, airdrop or compensation form, and it has no token to hand out.
Official places to read updates:
- The Arcus blog at arcus.xyz/blog, where the incident report sits.
- The status page at status.arcus.xyz.
- Arcus's X account @arcus_xyz and its Telegram announcements channel.
Every official web address ends in arcus.xyz. Anything with a hyphen, an extra word or a different ending is not Arcus. Our guide to Arcus scams and fake sites lists the real domains, shows what the fakes look like and covers what to do if you clicked one. Anyone offering to recover funds for a fee is running the second half of the same scam.
What this site cannot help with
For background on the venue itself, What Is Arcus covers who builds it and the trust assumptions in its design, Arcus and dYdX sorts out which company is which, and What Is Robinhood Chain explains the chain and its bridge.
Quoting a figure? Cite this page
Plain-text citation
Link to this page
Reuse. The figures on this page come from Arcus's incident report of November 10, 2026, the Arcus status page, Arcus's developer docs, Crypto Times (November 11, 2026) and Crypto Briefing (November 13, 2026). You may republish these figures with attribution and a link to https://arcusguide.com/privacy/arcus-exploit-november-2026.
Updates
- November 17, 2026: Page published. Arcus's status page reads All Systems Operational. Arcus's blog has no follow-up to the November 10 incident report, and Arcus has published nothing on fund recovery or the reported bounty offer.
Frequently Asked Questions
Arcus says no. Its incident report of November 10, 2026 states that the incident involved a single account, that no other user balances, positions or orders were affected, and that Arcus Labs covered the $2,234,391 USDG shortfall from its company treasury at 12:28 PM ET on November 10. That is Arcus's own account; no independent audit of the treasury top-up has been published.
Yes. Arcus re-enabled platform-wide withdrawals at 4:26 AM ET on November 10, 2026, about five hours after pausing them, and its incident report says trading and withdrawals are operating normally. On November 17, 2026 the Arcus status page read All Systems Operational.
Arcus says 2,234,391 USDG was withdrawn on-chain before withdrawals were stopped. A further 3 million dollars of withdrawal requests was held back by the bridge's on-chain rate limit, never paid out and later reversed, so that 3 million is not part of the loss.
Arcus describes an accounting bug in how the exchange handled transfers between a user's own sub-accounts, which let a newly created account record a balance far larger than it held and withdraw against it. Crypto Briefing reported on November 13 that the security firm CertiK attributes it to an integer underflow. Arcus has not published code-level detail.
Crypto Times reported on November 11 that the Defimon Alerts account shared an on-chain message, described as coming from the Arcus team, offering the exploiter 10 percent to return the other 90 percent by November 13. Arcus's incident report does not mention a bounty, and as of November 17 Arcus had not published whether any funds came back.
Independent resource: ArcusGuide is an independent, third-party resource operated by Concept211. It is not affiliated with, produced by, reviewed by or endorsed by Arcus Labs Ltd, Arcus Labs Inc., Pocket Protector Labs Inc., dYdX Trading Inc. (dYdX Labs), the dYdX Foundation, Robinhood or any of their affiliates. "Arcus" and related names and marks belong to their respective owners and are used here only to identify the platform this site documents. Read the full disclaimer.
Availability: Arcus perpetual contracts and derivatives trading features are not available to persons in the United States, Canada, the United Kingdom or other restricted or sanctioned jurisdictions, and Arcus restricts spot trading there too. This site is not intended for persons in those jurisdictions. Do not use a VPN or any other tool to get around a regional restriction; Arcus prohibits it.
Not advice: Nothing on this site is legal, tax, financial or investment advice. Descriptions of regulatory status, tax treatment and market availability are general information that varies by jurisdiction and changes over time. Confirm anything that matters to you with a qualified professional and against primary sources. Trading perpetual futures with leverage carries a substantial risk of loss, and past performance does not indicate future results.
Disclosure: this site contains referral links. Joining Arcus with code ARCUSGUIDE takes 5% off your trading fees and earns us a share of the fees Arcus already charges, at no extra cost to you.