
Arcus DEX loses $2.23M to accounting bug as bridge rate limit blocks $3M more
An accounting bug let an Arcus DEX account record a balance it never held and withdraw $2.23 million. A bridge rate limit blocked a further $3 million attempt.
In brief
- An accounting bug let a new Arcus DEX account record a balance far above its real holdings and withdraw $2.23 million.
- The bridge's on-chain rate limit blocked a further $3 million withdrawal attempt.
- Arcus fixed the flaw in about 90 minutes and covered the shortfall from its treasury.
What happened
Arcus DEX lost $2.23 million on 9 November after an accounting bug let a newly created account record a balance far larger than its actual holdings, according to Coin Bureau.
The account then withdrew funds it never owned.
The exploiter tried to take another $3 million.
The bridge's on-chain rate limit blocked those payouts before they were processed, Coin Bureau reported.
Arcus found and fixed the vulnerability in roughly 90 minutes.
It blocked the exploiter's addresses and paused withdrawals for a time.
The company covered the full $2.23 million shortfall from its treasury.
It said no other user balances, positions or orders were affected.
DefiLlama's hacks database lists the incident as a withdrawal logic flaw in the protocol logic on Robinhood Chain, with the $2.2 million returned.
Why it matters
The case shows how a single accounting error can drain a venue even when the exploit path is narrow.
It also shows a rate limit doing the job it was built for: the second attempt was stopped by a rule, not by a human.
The treasury backstop kept the loss off users' books.
Our earlier coverage of the Arcus Perps withdrawal logic flaw set out the same incident and the returned funds.
What to watch
The stolen funds are being tracked on-chain.
Arcus says it is working with blockchain investigators and law enforcement on recovery, according to Coin Bureau.