Arcus Exchange Loses $2.23 Million to Subaccount Accounting Bug, Covers Shortfall From Treasury
An accounting bug, not a hack of user wallets
Decentralised trading platform Arcus has disclosed that a newly created account exploited a flaw in transfers between user subaccounts to withdraw about $2.23 million in USDG it was not entitled to — and the company says it detected and fixed the bug within about an hour and covered the entire shortfall from its own treasury. User balances were unaffected, and trading and withdrawals are operating normally, according to the disclosure reported on November 11.
The incident is a useful reminder that some of the most expensive crypto losses do not come from stolen private keys at all. They come from ordinary accounting logic — the code that tracks who owns what inside a platform — being wrong in one narrow place. Follow security coverage like this on the Zimbuck News page.
What happened, step by step
According to Arcus's disclosure, summarised by PANews and corroborated by independent hack trackers that list the loss at about $2.2 million on November 10:
- At 11:07 on November 10 (Beijing time), a newly created account exploited a flaw in how the exchange processes transfers between user subaccounts.
- The bug let the account record a balance far higher than it actually held, and then request a withdrawal against that inflated balance.
- About $2.234 million in USDG was withdrawn on-chain before withdrawals were halted.
- A further withdrawal request of about $3 million was blocked by the cross-chain bridge's rate limit, was never paid, and was later cancelled.
- Arcus says it identified and fixed the bug within an hour, covered the shortfall in full from the company treasury, and published the attacker's initial address, asking exchanges and service providers to flag the related funds.
The platform is now working with blockchain investigators to trace the withdrawn funds. Independent trackers of verified November crypto thefts, such as the November 2026 verified
hacks report, also list the Arcus incident at roughly $2.2 million, matching the company's own figure.
Why the bridge rate limit mattered
The most underappreciated detail in this story is the control that worked. The attacker had already inflated the internal balance and queued far more than the $2.23 million that escaped — but the bridge's withdrawal rate limit stopped the extra $3 million from moving. Rate limits, withdrawal queues and staged limits for new accounts are unglamorous, yet they are exactly the kind of friction that turns a catastrophic drain into a containable one. It is the same defence-in-depth thinking behind the steps in our guide on protecting your accounts from SIM-swap hijacks: assume one layer fails, and make sure the next layer limits the damage.
How Arcus's response compares
Three parts of the response stand out. First, speed: detection and a fix inside roughly an hour limits how long an exploit window stays open. Second, the treasury cover: users did not wait for a recovery process or a token compensation plan, because the company absorbed the loss itself. Third, transparency: publishing the attacker's address lets other platforms freeze or flag funds before they are laundered further. The community discussion in the Zimbuck Market News group has seen this pattern before — compare it with how Across Protocol handled its domain hijack earlier this month, where compensation was also promised after the incident.
None of that makes the bug acceptable. A balance-inflation flaw in subaccount transfers is a core-ledger error, and platforms holding user funds are expected to test exactly those paths — deposits, internal transfers and withdrawals — hardest, because that is where an accounting mistake becomes real money leaving the door.
What users should take from this
For traders, the practical lessons are simple. Prefer platforms that publish incident reports with figures and timelines rather than vague statements. Be alert for fake "compensation" messages after any publicised exploit — scammers routinely impersonate affected platforms in the days after a disclosure, and Arcus users are no exception. And remember that a platform covering a loss from treasury is a sign of reserves and good process, not a guarantee about the next incident.
Frequently asked questions
Did Arcus users lose money? According to the company, no. Arcus covered the entire shortfall from its corporate treasury and says user balances were unaffected.
How much was actually stolen? About $2.23 million in USDG was withdrawn on-chain. A further request of about $3 million was blocked by the bridge rate limit and cancelled.
Was this a private-key hack? No. The disclosed cause was an accounting bug in transfers between subaccounts, which let a new account inflate its recorded balance.
Is trading back to normal? Arcus says trading and withdrawals are operating normally after the fix.
Security incidents like this are exactly why the Zimbuck community tracks exchange and protocol safety so closely — join us at Zimbuck for the next updates. This article is market news and general information only, not financial advice.