BLOCKCHAIN AI.NEWS

Security

A $350,000 Estimate, Not a Count: What Across Has and Hasn’t Said About Its Hijacked Domain

Attackers held across.to for roughly a night through a social-engineering attack on its registrar, Namecheap. The loss figure comes from GoPlus; Across has published neither a count nor a post-mortem.

Blockchain AI News default cover graphic
✓ First reported November 11 by The Block · FinanceFeeds · CryptoTicker · Loss estimate from GoPlus, flagging by SEAL911, incident classification by DefiLlama, as relayed by those outlets · Nov 11

Starting around 18:45 UTC on November 10, attackers took control of the domain for Across, the cross-chain bridge protocol, according to The Block. Visitors to the site were sent to a phishing page. By Wednesday, November 11, Across said it had the domain back and systems were running normally. In between, a number has been repeated by several outlets: about $350,000. It is worth being exact about where it comes from.

The timeline, as reported

The Block puts the takeover at roughly 18:45 UTC on November 10 and says Across received an alert within 15 minutes and began trying to take the site offline. The security group SEAL911 then flagged the domain as phishing with major wallet providers, and Cloudflare marked it at risk and removed its DNS records, which made the phishing page unreachable. CryptoTicker adds that Across warned users on X not to open the app, connect a wallet or sign anything, and temporarily shut down its web interface and API.

On the morning of November 11, Across said the domain was back under its control. FinanceFeeds reports that it regained it with help from Namecheap founder Richard Kirkendall and that third-party integrations and API users were unaffected. No smart-contract compromise has been disclosed in any of the three accounts this desk read.

What the phishing page asked for

The Block, citing GoPlus, says the page lured users into signing fake token approvals or permits that could drain their wallets. That matters for how the loss is counted. A signed approval or permit is a permission, and it can be used at any time after the signature. CryptoTicker makes the point directly: a permit signed on the fake page but not yet submitted on-chain does not show up in an approvals list. A wallet that has not yet lost funds is not necessarily a wallet that is safe.

One estimate, from a third party

The $350,000 figure is GoPlus’s. The Block reports GoPlus estimating total user losses at that level, with funds taken from wallets on Ethereum, Arbitrum, Base, BNB Chain, Ink and Plasma. FinanceFeeds says Across has not confirmed the figure and has not disclosed how many users were affected, and The Block says the same. CryptoTicker found no wallet count either; it says only that several users reported drained wallets, and it relays one user’s unconfirmed claim of losing 9,000 USDC and 7,053 USDT0 in seven transactions on Plasma.

CryptoTicker also notes a second figure, about $294,000, circulating in some media, and says it could not trace where that number comes from. This desk could not either, and does not use it.

What each party has said publicly, as of November 11

QuestionAnswer on the recordFrom
Total lossAbout $350,000 (estimate)GoPlus, via The Block and FinanceFeeds
Users affectedNot disclosedAcross
How the registrar was beaten“Social engineering”; no detailAcross
Namecheap’s accountNo public statement found by CryptoTicker; founder replied on X and opened an investigationCryptoTicker
Repayment“All affected users will be made whole”; post-mortem “in the coming days”Across, via CryptoTicker
Compiled from The Block, FinanceFeeds and CryptoTicker, each read by this desk on November 11.

The registrar is the open question

Across attributes the takeover to a social-engineering attack on Namecheap. FinanceFeeds notes that Across has not explained how the registrar’s account controls were defeated, and CryptoTicker says the cause currently rests solely on Across’s account and that Namecheap has not publicly commented on what happened. Both can be true without anyone being careless: a registrar is a customer-support process as much as a login, and attacks on that process do not touch a protocol’s own keys. But until Across or Namecheap says what was impersonated and which check failed, the specific failure is unknown. This desk does not know whether it was an employee’s account, a support request or something else, and none of the sources say.

If you used the site on November 10 or 11

CryptoTicker’s guidance is the practical part. Check your token approvals on Revoke.cash or Etherscan’s approval checker; look for approvals dated November 10 or 11, unknown addresses or unlimited amounts, and revoke them. If you signed a permit on the fake page and still hold funds, move them to a new address, because an unsubmitted permit will not appear in those lists. Keep your address, transaction hashes and screenshots. Be wary of unsolicited refund or support messages; use only Across’s official channels.

The same day, a different failure: Arcus

The Block’s report also covers a separate incident. Arcus, a decentralized exchange, lost 2,234,391 USDG, about $2.23 million, according to FinanceFeeds, which says DefiLlama classifies it as a protocol-logic exploit involving a withdrawal flaw. FinanceFeeds describes the mechanism as an accounting flaw in transfers between subaccounts that let one account record a balance larger than the funds it held; the attacker then withdrew against the inflated figure.

The attacker tried to withdraw roughly another $3 million, and the bridge’s withdrawal rate limit blocked those requests, per both outlets; FinanceFeeds says the pending transactions were later reversed. Arcus paused withdrawals, patched the accounting issue, restricted the exploiter’s accounts and reopened withdrawals. Arcus Labs said it covered the full $2.23 million shortfall from company treasury funds and that other customer balances, positions and orders were unaffected. Those statements are Arcus’s own, relayed by FinanceFeeds. The two incidents appear unrelated.

For scale, The Block cites DefiLlama data showing $8.78 billion lost across 341 hacks and exploits so far this year, led by a $6.36 billion Binance breach.

The Take

Across’s contracts, so far as anyone has said, did their job; the exposure was a website address held at a third party. That is the useful lesson, and also the reason a precise accounting matters: a bridge that says “made whole” has made a promise whose size nobody outside the company can check. A $350,000 estimate from a security vendor is a reasonable starting point. The post-mortem should replace it with a count of wallets, a total, and a plain account of what the registrar was talked into.

More on the subject