The Ledger
Arcus says treasury covered $2,234,391 USDG withdrawal
Arcus says an accounting bug allowed a newly created account to withdraw $2,234,391 USDG before the exchange stopped withdrawals. The company says it covered the shortfall from its treasury and is tracking the withdrawn funds.

An account withdrew $2,234,391 USDG on-chain after exploiting an accounting bug on Arcus, the exchange says. Arcus says its company treasury has covered the resulting shortfall.
In its November 10 incident report, the exchange says a further $3 million in requested withdrawals was held back by the bridge's on-chain rate limit, never paid out and later reversed. The incident involved a single account, and other users' balances, positions and orders were unaffected, according to the report.
Inflated balance
The activity began around 10:07 p.m. Eastern time on November 9, according to Arcus. The newly created account exploited a bug in how the exchange handled transfers between a user's own subaccounts.
Under specific conditions, the flaw let the account record a balance far larger than it actually held, the exchange says. The account then requested withdrawals against that inflated balance.
Withdrawal pause and fix
Arcus says the bridge's withdrawal rate limit capped payouts at 10:10 p.m. on November 9 and held back the additional $3 million in requests. Its monitoring flagged the withdrawals at 10:15 p.m., and the team began investigating.
The team paused withdrawals across the platform at 11:07 p.m. and updated its status page, according to the incident report. The exchange's timeline records deployment of the fix at 11:37 p.m. and says the team blocked the exploiter's addresses from trading, transferring and withdrawing at 11:43 p.m.
The team re-enabled platform-wide withdrawals at 4:26 a.m. Eastern time on November 10, according to the timeline. It reversed pending withdrawals from the exploiter at 5:02 a.m., and Arcus Labs covered the shortfall from its treasury at 12:28 p.m.
The report's opening says the bug was detected and fixed within one hour. Its detailed timeline separately lists the monitoring alert at 10:15 p.m. and deployment of the fix at 11:37 p.m.
Tracking the funds
Arcus says its security partners reviewed the fix and related checks across the codebase. The exchange says it is continuing to improve its systems for detecting and mitigating suspicious activity.
The company says it is working with blockchain investigators and will coordinate with law enforcement as appropriate. It says the withdrawn funds are being tracked on-chain.
Arcus published what it identified as the exploiter's initial address, 0xeFbf442599310E5CeE1A4EDd5c66334c5f30b3Dd. The exchange asked exchanges and service providers to flag any funds received from that address.
Sources
- Original source · Blog post Arcus arcus.xyz
Related stories
- Paxos USDG Had $2.81B in Adjusted Supply on Nov. 5
- Arbitrum DAO’s USDG Proposal Passes Offchain Vote With 199.5M ARB in Favor
- Curve says fee-burner flaw let attacker take about $38,200
- Aave Freezes 292 Reserves After Exploiter Borrows $44.6M
- Scroll replaces mainnet proof verifier after vulnerability report