Across has recovered its crypto bridge website after an attacker turned its familiar address into a trap for wallets. The service helps people move crypto between networks. It reported normal operations at 8:16 p.m. Eastern on November 10, which was already November 11 in UTC. [1] [4]
The return of service leaves a separate money problem. Blockchain investigator Bitquery estimates that nine wallets lost about $348,000 during the November 10 attack. Across has promised to repay affected users, but restoring the website does not cancel malicious spending permissions already signed. [3] [5] [6]
View the incident and remaining risk
| Part | What the evidence says |
|---|---|
| Web address | Across says an attacker took control at about 18:45 UTC on November 10. |
| Fake page | The recovery guide describes permissions that let attacker-controlled contracts move users’ tokens. |
| Site restored | Across reported recovery at 01:16 UTC on November 11. |
| Wallet permissions | The guide warns that some remain active and can affect tokens arriving later. |
Arrows show a simplified sequence, not measured duration or transfer volume. The reported restoration time is the statement’s timestamp, not an independently measured recovery time.
The real address led to a fake page
Across says someone tricked its domain registrar, Namecheap, into handing over control at about 18:45 UTC on November 10. A registrar manages a website’s name and where it points. Across said it was alerted within 15 minutes. [2]
Visitors could therefore reach the attacker’s page while using the address they recognized. Bitquery’s investigation describes a copy that asked people to sign requests allowing tokens to leave their wallets. This was a website takeover, rather than evidence that the bridge’s underlying blockchain code had been broken. [3]
“Across is fully restored, and all systems are operational.”
Across, November 11, 2026 (UTC) [1]
A familiar route for moving crypto
Across also works behind other companies’ apps. Uniswap’s help page explains that Across completes swaps between networks by arranging for tokens to arrive on the destination network. That makes it part of the route people use to move trading funds, rather than just another token website. [4]
The distinction matters for the scope of this attack. Across said third-party integrations and users of its programming interface were unaffected, according to Bitquery’s investigation. Losses at the fake website do not establish that every app using the bridge was compromised. [3]
Bitquery’s estimate also shows how uneven the damage was: about $305,000 came from one depositor. Its figures are an investigator’s reconstruction, rather than a final loss total issued by Across. [3]
The site is back; wallet exposure can remain
Across’s November 10 follow-up pledged to make affected users whole. That is a repayment promise, not evidence that reimbursements have finished. [5]
Its recovery guide warns that some permissions granted to attacker-controlled contracts remain open. Those permissions can let an attacker take more tokens that later enter an affected wallet. The guide also distinguishes stopping future theft from recovering money already taken, and warns that signed but unused permissions may not yet be visible. [6]
The takeaway
Across has restored access, but the recovery still has two unfinished parts: resolving exposed wallets and delivering the promised repayments. A working website alone does not settle either one.
