Zimbuck – Your Market. Your Community.

Across Protocol Recovers Website After Domain Hijack Sent DeFi Users to a Phishing Page

5 min read
0
Comments
278
Views

Across Protocol, one of the largest cross-chain bridges in DeFi, has regained control of its across.to website after an attacker hijacked the domain on November 10 and pointed visitors at a phishing page. The bridge's smart contracts were not exploited, Across says all affected users will be made whole, and the incident is a sharp lesson in DeFi's weakest layer: the website, not the code.

The bridge-safety discussion is running in the Zimbuck Market News group — including what anyone who used the site on November 10 should do now.

What happened to Across

Across says an attacker took control of the across.to domain at about 18:45 UTC on November 10 through a social engineering attack on its domain registrar, Namecheap, and replaced the real site with a phishing page designed to drain wallets. The team says it was alerted within about 15 minutes and moved to shut the site down. The security response group SEAL911 helped flag the domain as phishing with major wallets, while Cloudflare marked it at risk and later removed its DNS records.

On Wednesday, Across said the domain was back under its control, with help from Namecheap founder Richard Kirkendall, and that all systems are working normally, according to Cointelegraph's report on the recovery.

  • Attack start: about 18:45 UTC, November 10, via registrar social engineering
  • What was hit: the website frontend only — bridge smart contracts not exploited
  • Bridge scale: about $5.9 billion processed in the prior 30 days, third among bridges by transfer volume (DefiLlama)
  • Response: frontend and API taken offline; SEAL911 and Cloudflare flagged the domain
  • Outcome: domain recovered; Across pledges to make all affected users whole

How much was lost — and what is not confirmed

Security firm GoPlus estimates nearly $350,000 was drained across six chains — Ethereum, Arbitrum, Base, BNB Chain, Ink and Plasma — via malicious token approvals, EIP-2612 permits and Permit2 authorisations signed on the fake site, or funds sent directly to attacker addresses. Across itself has not confirmed that figure and has not disclosed its own loss total or the number of affected users, and individual user loss reports circulating online have not been independently verified. The verified facts are the hijack, the phishing page and the recovery — treat any specific loss total beyond GoPlus's estimate as unconfirmed until Across publishes its post-mortem, which it says is coming in the next few days.

The mechanics matter for every DeFi user. A phishing frontend does not need to break a contract: it only needs you to sign. Approvals and permits signed on the fake site can let an attacker move tokens later, even after the real site is back — which is why frontend attacks keep working against audited protocols. Our explainer on how crypto bridges move funds between chains covers what the underlying bridge does when it is working normally, and our SIM swap attack guide covers the account-takeover cousin of this registrar-level attack.

What affected users should do

Across's recovery guidance is aimed at anyone who visited the site and connected a wallet on November 10. Its core steps: check every network you used, starting with the one where you used the frontend, and revoke token approvals and permits granted that day — Across points users to type revoke.cash into their browser themselves rather than following revocation links sent by message or email, which are a classic second-wave phishing trick. Until approvals are revoked, a malicious permit can still be used against tokens that arrive in the wallet later. Users who only used third-party integrations or the API were not affected, Across says.

More DeFi coverage and protocol news is collected on the Zimbuck News page.

FAQ

Was the Across bridge hacked?
The bridge's smart contracts were not exploited. What was hijacked was the website domain, via a social engineering attack on the registrar — visitors were shown a phishing page instead of the real app.

How much money was lost?
Across has not disclosed a total. Security firm GoPlus estimates nearly $350,000 across six chains, but Across has not confirmed that figure, and individual user reports are unverified.

Will affected users be reimbursed?
Across says all affected users will be made whole. Details are expected in the full post-mortem the team has promised in the coming days.

I connected my wallet to across.to on November 10. What should I do?
Follow Across's recovery guide: review and revoke token approvals and permits you granted that day on every network you used, typing the revocation tool's address into your browser yourself rather than clicking links sent to you.

How can DeFi users protect against frontend hijacks?
Bookmark official app addresses, double-check the domain before connecting, be wary of unlimited token approvals, and revoke approvals you no longer need. A correct contract cannot protect a signature you gave to a fake page.

Join the conversation on Zimbuck — the finance social platform for traders and investors — to follow the Across post-mortem when it lands. This article is market news and general information only, not financial advice.