UPDATED 04:49 UTC, 11 Nov: Across says the cause was a social engineering attack on its domain registrar, Namecheap, at about 18:45 UTC on 10 Nov, which gave an attacker control of the Across domain and put a phishing site on it (Across on X). Across says it was alerted within 15 minutes; SEAL 911 had the domain flagged as phishing with major wallets, and Cloudflare marked it as at risk and later pulled its DNS records. Some people who visited the site before it was blocked may have been affected; users of the Across API and of third-party integrations were not, the team says. At 01:16 UTC on 11 Nov Across said the domain was back under its control and all systems were working normally (Across on X). “All affected users will be made whole,” it said, and a full post-mortem will follow in the coming days. Across has not given a loss figure or a count of affected users. If you connected a wallet to the Across site on 10 Nov, revoke any approvals granted that day, as Across advises (Across on X), and deal with the team only through its official accounts.

SECURITY ALERT

The contracts may be fine.

The front door is the problem.

Across, a bridge that moves tokens between Ethereum and other chains, posted an alert on X at 19:05 UTC on Tuesday: it is “investigating an issue with the Across domain”, and users should not visit the app, connect a wallet, or sign any transaction or approval there “until further notice”.

That is the whole of the official statement so far. Across has not said what the issue is, when it began, or whether any funds were taken.

What users are saying

Within minutes, replies to the alert began describing losses.

Several users said their wallets were emptied after bridging through the site on Tuesday evening. One said the website had been compromised. Across replied to one of them asking for the transaction details so it could investigate, and asked others to send direct messages.

We have not verified any of these claims. Across has not confirmed a loss figure, and none should be treated as one.

The Defiant, which reported the alert, noted that it does not establish whether the bridge’s smart contracts or bridging operations are affected.

So what, exactly, is broken?

Why a domain matters

A bridge has two parts. The contracts on each chain hold and release the funds. The website is the page that builds the transactions your wallet is asked to sign.

If an attacker controls the domain, through a hijacked registrar account or altered DNS records, the site can look normal while asking you to sign something else: an approval that lets a third party move your tokens, or a transfer to an address you never chose. The contracts then do exactly what the signature tells them to.

That is how hijacked domains turned a dozen DeFi sites into wallet drainers on 31 Oct.

We do not know yet whether that is what happened at Across. No attacker has been named, and we do not name one.

How long before the all-clear?

Protect yourself

  • Do not open the Across app, connect a wallet or sign anything on it until Across says on its official accounts that the site is safe.
  • If you bridged or signed an approval through Across on 10 Nov, check your wallet’s token approvals with a revoke tool and remove any you do not recognise.
  • Keep your transaction hashes, and send them only through Across’s official channels; treat any “refund” or “recovery” offer that reaches you first as a likely scam.

Corrections and new evidence: [email protected]

This article is for information only and is not investment advice.