Across Protocol Phishing Attack: Crypto Domain Hijacking 🔥
Discover the Across Protocol phishing attack: crypto domain hijacking redirected users to a DeFi phishing site. Learn crypto wallet & cross-chain bridge security.

Across Protocol's Domain Hijack: What Happened and What It Means
A website can be the front door to a crypto app - and sometimes the weak link. In this case, Across Protocol says attackers used social engineering against its domain registrar to take control of its website address and redirect visitors to a phishing page. The incident led the team to warn users to stay away from its app, while reports of drained wallets started to circulate.
Across later said it had regained control of the domain and that its systems were operating normally. It also said affected users would be made whole, but it hasn't yet published how many users were impacted or the total losses. Those details matter: getting the domain back isn't the same thing as fully accounting for what users did or lost. And a phishing incident alone doesn't prove that a bridge's smart contracts were compromised.
This article separates what the protocol says from what still isn't clear, explains how a hijacked domain can create wallet risk, and lays out practical checks for users and crypto teams. The core takeaway is operational: control of the website, the app, the domain, and the underlying contracts are related - but they're not the same risk.
What happened in the Across Protocol incident
Across Protocol says an attacker gained control of its domain via social engineering aimed at its registrar, Namecheap. The team placed the takeover at about 18:45 UTC on Tuesday, and said it was alerted within 15 minutes and moved to shut down the website.
With domain control, attackers can swap the legitimate site for a phishing page. That's the danger: a visitor can land on a correct-looking address and still be shown malicious content if the domain or DNS has been redirected. If the user trusts what they see, they may connect a wallet or approve a transaction without realizing they're no longer interacting with the protocol's intended interface.
The response and recovery timeline
Across said it regained control of the across.to domain on Wednesday, with help from Namecheap founder Richard Kirkendall. The team said everything was working normally again and promised a full post-mortem in the coming days. It also reiterated that affected users would be made whole, but it still hasn't published total losses or the number of impacted users.
Across described a multi-party response. It said its security response group SEAL911 helped flag the domain as phishing with major wallets. Cloudflare marked the domain as at risk and later removed its DNS records. These steps can reduce how many people reach the malicious page, but they can't undo transactions someone already signed.
Across's initial warning came after reports of drained wallets. The point of the warning was to avoid the app while the team investigated. What's still missing is basic incident scope: how many people visited the phishing page, how many signed transactions, and how much was lost. Until those numbers are verified, the public record shouldn't try to infer the answers from "wallets were reportedly drained."
What the incident does - and does not - establish
According to Across, the confirmed issue was domain control after a registrar-focused social engineering attack. That's not the same as evidence that an attacker exploited a vulnerability in Across's bridge contracts. The distinction matters, but it shouldn't be used to hand-wave the risk: crypto users act through interfaces, and a deceptive interface can still lead people to approve harmful transactions.
Across also said third-party integrations and API users were unaffected. That statement is about the scope the team reported - not independent proof that nothing else was touched. A detailed post-mortem should explain what systems were affected, how the attacker got in, how long the exposure lasted, and what checks confirmed that recovery.
How a domain hijack can put wallets at risk
A domain sits inside a crypto product's security boundary because it determines where a user's browser goes when they type the address or click the app link. If an attacker controls that domain, they can present a counterfeit interface under a name the user already recognizes. Familiarity lowers suspicion faster than random links in a message.
In many cases, the attacker doesn't need to steal a seed phrase. A phishing page can prompt a wallet connection or present an approval request. Wallets typically display transaction details, but those details can be easy to miss - especially when a user is expecting a normal bridging flow and just wants to finish the task. The harm usually comes from signing or approving permissions, not from merely opening the page.
The path from a registrar account to a malicious transaction
A simple chain of events looks like this:
- An attacker persuades or manipulates a registrar support process to change access or account settings.
- Control of the domain or its DNS configuration changes.
- Visitors get routed to a page controlled by the attacker.
- The page imitates the expected product and asks visitors to connect a wallet or approve an action.
- A user signs a transaction that can move assets or grant permissions.
Across hasn't fully disclosed the exact technical sequence in its updates. The steps above describe the general risk pattern, not a confirmed reconstruction of every action taken in this incident. The post-mortem should clarify whether the attacker gained access to a registrar account, changed DNS, altered hosting, or combined multiple failure points.
Why the response has to cover more than the website
Taking a site offline can stop more people from reaching a malicious page. It doesn't automatically secure the underlying registrar account, revoke suspicious approvals, or identify transactions that were already signed. Recovery therefore has multiple tracks: regain and verify domain control, remove malicious DNS or content, warn users through trusted channels, coordinate with wallets and security responders, and investigate any on-chain effects.
For users, the practical message is straightforward: don't treat a familiar URL or a page that "looks right" as proof that interacting with it is safe during an active incident. Pause before signing. Check what you're being asked to approve - especially token allowances and transfers that aren't what you expected. If you interacted with a suspected phishing page, note the time and the transaction details, then follow the protocol's incident guidance through channels you can verify independently.
What was affected and what remains unknown
Based on the reported updates, the incident affected Across's website domain. Across says it regained control and that its systems were operating normally, and it also claims third-party integrations and API users weren't affected. Those points narrow the scope the team is describing - but they don't answer every question users, integrators, or risk teams would ask.
As of the latest updates referenced here, Across hadn't published the total value of losses or the number of affected users. It also hasn't released the promised full post-mortem. Until that report is available, the public record leaves major gaps around exposure, transaction impact, and which controls failed (or were bypassed).
Domain control is not the same as bridge integrity
A bridge's website, APIs, smart contracts, and operational infrastructure are different components. A domain compromise can make the user interface unsafe without proving that the bridge contracts themselves were changed. On the other hand, restoring a website doesn't automatically mean every other component was checked independently and found clean.
That's why careful incident language matters. Users shouldn't assume that all funds are at risk, and they also shouldn't assume it was harmless just because the website is back. The evidence in the cited updates supports a narrower conclusion: Across reported a domain hijack and phishing exposure, then reported recovery. The extent of user losses is still not disclosed in those reports.
Why the protocol's size is relevant - but not proof of impact
Across was a significant cross-chain bridge by activity. The report placed it third for 30-day transfer volume, behind Circle and LayerZero, and cited about $5.9 billion in volume over that period, according to DefiLlama. That figure describes overall activity during the measurement window - it isn't a measure of what was stolen in this incident, the bridge's total value locked, or the number of impacted users.
High usage does raise the stakes for communications and reach. A phishing page targeting a widely used bridge can potentially reach more people than one aimed at a low-traffic service. It also makes clear communication more urgent: users need a trusted alert quickly, while wallets and integrators need enough information to decide whether to block or warn. Still, volume by itself can't tell you how many visitors hit the malicious page or how many signed a harmful transaction.
A useful post-mortem should answer at least four questions: the initial access path, how long and how broadly the malicious routing reached users, a verified impact assessment for users and finances, and what safeguards were added afterward. Without that, specific claims about losses or technical root cause remain unverified.
What crypto teams and users should do next
A domain registrar account often gets treated like routine infrastructure, while the real engineering focus goes toward smart contracts and cloud systems. The problem is that domain control is a dependency with real risk: it's the address users trust, and a compromised registrar account can put a convincing fake in front of them. Teams should treat registrar access like a production security control, not an administrative afterthought.
A practical checklist for crypto teams
- Protect registrar access. Use unique credentials, strong multi-factor authentication, and restrict access. Keep recovery steps documented, and add extra verification for ownership, DNS changes, or account recovery.
- Separate critical roles. Don't rely on one person - or one inbox - for domain administration and emergency recovery. Separation can slow an attacker, and redundant ownership helps prevent a stalled response if the primary contact is unavailable.
- Monitor for unexpected changes. Track registrar logins, nameserver edits, DNS record changes, and certificate/hosting changes. Monitoring is only useful if someone is actually on call and knows what to do when an alert hits.
- Prepare an incident channel. Set up ways to reach users that don't depend on the compromised domain. Decide who can publish warnings, who coordinates with wallets and infrastructure providers, and how the team confirms a message is authentic.
- Define a stop condition. Decide in advance when to disable the app or show a warning. A short outage is painful, but continuing to route users to a suspect interface can turn uncertainty into more harm.
- Test recovery, not just prevention. Rehearse domain recovery with the registrar and relevant providers. A runbook that hasn't been tested under pressure can fail - especially when normal support processes are part of the threat path.
There's a trade-off here: if you add heavy approval steps to every routine domain change, you can slow legitimate work to a crawl. The goal isn't "maximum friction everywhere." Put stronger checks on changes with high impact - ownership, recovery credentials, nameservers, and production DNS - and keep low-risk updates efficient.
A user checklist during a suspected phishing incident
- Stop using the app until the protocol confirms the incident is contained through channels you can verify independently.
- Don't connect a wallet or sign transactions prompted by the suspicious page.
- If you already signed, review the transaction and any token approvals using a wallet or security tool you trust. Revoke permissions if appropriate, but don't click unsolicited links or "help" messages.
- Save transaction hashes, timestamps, and relevant screenshots. Those details can help the protocol investigate and evaluate reimbursement eligibility.
- Wait for a clear incident update before resuming. A domain returning to normal is a good sign - but it doesn't replace understanding whether your wallet interacted with the malicious site.
Also be careful with anyone offering "direct recovery help." Phishing incidents often lead to a second wave of scams targeting people who are worried about losses. Don't share a seed phrase or private key with anyone; no legitimate incident response process needs that.
Key takeaways
- Across said the takeover involved social engineering targeting its registrar, not a disclosed smart-contract exploit.
- The team said it regained the domain, restored normal operations, and would reimburse affected users; it still hadn't published losses or the number of impacted users.
- A domain can return to normal while questions about exposure and user transactions remain unresolved.
- For teams, registrar security and tested user communications should be part of the incident plan. For users, the decisive safety check is whether a transaction is expected and understood before signing.
Conclusion
Across Protocol's domain takeover is a reminder that crypto security doesn't stop at smart contracts. The website address, registrar account, DNS configuration, wallet interface, and user communication channels all influence whether people reach - and trust - the right product.
Across says it recovered its domain, restored normal operations, and plans to reimburse affected users. The size and mechanics of any user losses are still unclear in the updates so far, which makes the promised post-mortem the next step. For users, pause before signing during an active incident. For teams, secure the domain as production infrastructure and rehearse how to pull the interface offline, warn users, and verify recovery.