At 11:07 a.m. Beijing time on November 10, a newly registered account went to work on Arcus. Arcus is a perpetuals exchange on Robinhood Chain, which launched alongside the chain this July. The account never deposited a cent. It just shuffled funds among a few of its subaccounts, and suddenly its ledger showed a balance it didn’t have. Then it withdrew 2,234,391 USDG—real funds, taken straight off the chain.
USDG is a dollar stablecoin issued by Paxos and serves as the settlement currency on Arcus. At $2.23 million, it amounted to about 3.5% of the $63.6 million locked across Arcus. No private keys were lost, and no contracts were breached; the problem was in the exchange’s own accounting logic. Transfers between subaccounts should be like moving money from one pocket to another: the total shouldn’t change. But under certain conditions, the receiving subaccount was credited extra funds while the sending account wasn’t fully debited, making the balance appear out of thin air. The system trusted its own ledger and approved the withdrawal.
Three minutes later, the bridge’s withdrawal rate limit kicked in. At 11:10 a.m., the cross-chain bridge’s withdrawal limit held up subsequent requests, and another $3 million withdrawal didn’t go through and was later canceled outright. At 12:07 p.m., withdrawals across the entire platform were paused. A patch went live at 12:37, and six minutes later, the attacker’s address was blocked. Withdrawals resumed at 5:26 p.m. that day, and by 1:28 a.m. the next day, the company had filled the shortfall with its own money. No other users’ balances, positions, or open orders were affected; only this one account was impacted.
The on-chain funds still haven’t been recovered. Around noon that day, the attacker’s address received about 1,052 ETH. Later, around 53 ETH was sent to THORChain. By November 11, about 475 ETH remained, worth nearly $980,000 at the time. Public reports haven’t explained where the several hundred ETH in between went. Arcus disclosed the attacker’s initial address, asked others in the industry to flag the associated funds, and said it was working with on-chain investigators.
There are two things about this incident worth a closer look. First, where the vulnerability was. Many people think the security of decentralized exchanges is just about whether the smart contracts have been audited. But the problem this time was in the off-chain accounting code, a layer that outsiders have a hard time auditing. The second is what actually stopped the losses. Neither audits nor private-key management helped. In the end, what worked was a very mundane rule: the cross-chain bridge had a limit on how much could be withdrawn per hour. Without that rate limit, the loss would have been $5.23 million instead of $2.23 million.
Arcus says it discovered and fixed the vulnerability within an hour. But its own timeline adds up to about 82 minutes from the monitoring alert to the patch going live, and about 90 minutes from the start of the attack. The accounts don’t match, but the shortfall really was covered quickly: the company paid out of its own pocket, and users didn’t share the loss. A full root-cause report hasn’t been published yet, so it’s still unclear what conditions triggered the duplicate credit.
For retail investors, the real takeaway from this incident is to pay attention to every platform you use. When you keep your money on an exchange, security isn’t just about whether it has been audited. You also need to consider whether anyone is monitoring its internal accounting, whether withdrawals are rate-limited, and whether someone will make users whole if something goes wrong. These three things may not appear in an audit report; you can only judge by how the platform handled past incidents. Arcus handled this one fairly swiftly: within a dozen hours, it replenished the funds, resumed withdrawals, and published the address. Those are all signs of a responsive approach, but the money being returned is what counts.
Exchange security has two layers: keeping thieves out and making users whole. There will always be some thieves who get through; this time, the vulnerability was in the company’s own ledger. The safety net is what retail investors can really count on. Rate limits, pausing withdrawals, and the company covering the loss—without any one of these, the outcome would have been much worse. The next time you open an account on a new platform, don’t start by looking at how much it offers in fee discounts. Check whether it has had incidents before, and how it handled them.
Do you know whether the exchange you use has per-transaction or daily withdrawal limits?
#Arcus #RobinhoodChain #黑客攻击 #Web3安全 #DecentralizedExchange
—— Web3 leek Xiaokai
This content reflects personal opinions only and does not constitute investment advice. Please make your own judgment.