Across Protocol domain hijacked via Namecheap social engineering; bridge restored, affected users to be made whole
Attackers took control of cross-chain bridge Across Protocol's across.to domain on November 10, 2026 after what Across called a social engineering attack on its registrar, Namecheap, and replaced the site with a phishing page that drained some visitors' wallets. Across says the domain is back under its control, all systems are operational, affected users will be made whole and a post-mortem is coming. Total losses have not been officially disclosed.

Table of Contents
Cross-chain bridge Across Protocol says it has regained control of its website after attackers hijacked its across.to domain on Tuesday, November 10, 2026, and briefly replaced the real app with a phishing page. According to Across, the takeover started with a social engineering attack on its domain registrar, Namecheap, not with a flaw in the protocol's smart contracts. Several users reported drained wallets while the fake site was live. Across has promised that all affected users will be made whole and says it will publish a full post-mortem in the coming days. This Across Protocol domain hijack is a reminder that in crypto, the website you type into your browser can be as much of a target as the code on-chain.
What happened, step by step
In a detailed post on its official X account at 22:13 UTC on November 10, Across said that at about 18:45 UTC a social engineering attack on Namecheap gave a bad actor control of the Across domain. The team said it was alerted within 15 minutes and immediately worked to shut the site down.
Across said the security response group SEAL911 flagged across.to as a phishing site with major wallets, and that Cloudflare helped mark the domain as at risk and later pulled the site's DNS records, which took the malicious page offline. At the time of that post, the frontend and API were fully down. Across also said that, despite its efforts, Namecheap had been unresponsive at that stage, so it could not yet bring its services back safely.
Earlier, at 19:05 UTC, Across had posted an alert telling users not to visit the app, connect a wallet, or sign any transaction or approval there until further notice. That first warning did not explain what had happened; the cause was disclosed about three hours later.
At 01:16 UTC on November 11, Across said the bridge was "fully restored," that across.to was back under its control and that all systems were working normally. It thanked Namecheap's founder, who posts on X as @synth, for responding, helping it secure the account and opening an investigation. In a later reply, Across added that integrators were not affected and that all services were fully restored. Cointelegraph identified Namecheap's founder as Richard Kirkendall. MyTraderBot did not find a separate public statement from Namecheap about the incident at the time of writing.
Timeline (all times UTC, as reported by Across and the cited outlets)
About 18:45, November 10: attacker gains control of the Across domain, according to Across.
19:05, November 10: Across posts its first public alert telling users not to use the app.
22:13, November 10: Across explains the Namecheap social engineering attack, the SEAL911 and Cloudflare response, and the compensation pledge.
01:16, November 11: Across says the domain is back under its control and all systems are operational.
04:34, November 11: GoPlus Security publishes an alert describing the incident as a DNS hijacking attack.
Who was affected and how much was lost
Across said the risk was limited to people who visited across.to during the short window before Cloudflare fully blocked the malicious site. It said users of its API, third-party integrations, and people who used the Across frontend before the attack were not affected and are completely safe.
Across itself has not published a loss figure. Crypto news service CoinNess, citing Web3 security firm GoPlus, reported that total user losses were estimated at about $350,000, with funds taken from wallets on Ethereum, Arbitrum, Base, BNB Chain, Ink and Plasma. That number is a third-party estimate and could change once Across releases its post-mortem.
On X, individual users described their losses in replies to Across. One user said they lost $9,000 in USDC, and another said 7,053.46 USDT0 was taken from their wallet on the Plasma chain across seven transactions. Cointelegraph reported these claims but said it had not independently verified them, and MyTraderBot has not verified them either. Across asked affected users to send transaction details and replied that it was contacting them by direct message.
Why a domain hijack is so dangerous
Across is a large bridge. Citing DefiLlama data, Cointelegraph reported that Across ranked third among bridges by 30-day transfer volume, behind Circle and LayerZero, with about $5.9 billion processed over that period. A bridge frontend asks users to connect a wallet and sign approvals as part of normal use, so a fake copy of the site can look entirely routine.
In a domain hijack, the attacker does not need to break the protocol's contracts. Taking control of the domain's registration or DNS lets them point the real address to a server they run. The browser still shows the correct name, so checking the URL alone does not help. The fake page then asks for token approvals or signatures that let the attacker move funds. This is different from a smart contract exploit: the contracts can stay intact while users lose money through the website.
It is not the only recent incident covered on MyTraderBot in which the weak point sat outside the core smart contracts. Earlier, Keplr paused Google and Apple social login after a reported breach at its key provider (https://mytraderbot.online/en/news/keplr-pauses-google-apple-login-web3auth-key-breach), and Initia halted its layer 1 after unauthorized escrow transfers (https://mytraderbot.online/en/news/initia-l1-halted-unauthorized-escrow-transfers-rollup-keys). Phishing and impersonation also drove the recent alleged Binance user data sale, which turned out to be a likely scam (https://mytraderbot.online/en/news/binance-alleged-335-million-user-data-sale-likely-scam).
What Across users should do now
If you visited across.to on November 10 and connected a wallet or signed anything, Across asks you to contact it by direct message on X with your transaction details. Only use the verified @AcrossProtocol account and be wary of anyone who contacts you first offering "recovery" help, because scammers often target victims after a hack.
Across also recommends going to revoke.cash with the wallet you connected and revoking any permissions granted that day. In general, it is a good habit to review token approvals regularly, to bookmark the sites you use rather than following links from search ads or social media, and to read what a wallet asks you to sign. A hardware wallet with clear transaction previews can make a malicious approval easier to spot, but it does not replace checking what you sign.
Across said some wallets or browsers may still show phishing warnings for a while after the restoration, according to ChainCatcher's report. Those warnings should clear as security lists update.
What to watch next
The key open questions are how the attacker got past Namecheap's account protections, how much was actually lost, how many wallets were affected, and how and when Across will compensate users. Across said its domain was locked down with strong security practices and that the takeover "should not have been possible," so the post-mortem may shed light on registrar-level risks that affect many crypto projects, not just Across. Any comment or findings from Namecheap's investigation will also matter.
FAQ
Were Across smart contracts hacked?
According to Across, no. The company says attackers took over its domain through a social engineering attack on Namecheap and served a phishing site. It has not reported any contract exploit.
Is Across safe to use now?
Across says the domain is back under its control and all systems are operational. Users should still access the app only through the official address and verify approvals before signing.
Will victims be compensated?
Across has said all affected users will be made whole, but it has not yet published the details or timeline of the reimbursement.
Sources & further reading
- Across Protocol on X: first alert, 10 Nov 2026 19:05 UTC
- Across Protocol on X: incident explanation, 10 Nov 2026 22:13 UTC
- Across Protocol on X: affected users and revoke guidance, 10 Nov 2026 22:13 UTC
- Across Protocol on X: services restored, 11 Nov 2026 01:16 UTC
- GoPlus Security on X: alert, 11 Nov 2026 04:34 UTC
- Cointelegraph: Across warns users to avoid app, 10 Nov 2026
- Cointelegraph: Across restores website after domain hijack, 11 Nov 2026
- CoinNess: losses estimated at $350K (citing GoPlus), 11 Nov 2026
- ChainCatcher: Across regains domain control, 11 Nov 2026
- Featured image: AI-generated illustration by MyTraderBot (not a photo)
See the signals and their results
Browse publicly logged signals and how they performed, or create a free account to follow them.





