Across Protocol Domain Hijacked via Namecheap Social Engineering Attack, Users to Be Made Whole

Across Protocol Domain Hijacked via Namecheap Social Engineering Attack, Users to Be Made Whole


Across Protocol, a cross-chain bridge that lets users move crypto assets between blockchain networks, has regained control of its official website. On November 10, 2026, an attacker hijacked the site’s domain and replaced it with a phishing page. The team said the attacker got in through a social engineering attack on its domain registrar, Namecheap, and that every affected user will be compensated.

Across Protocol’s domain hijack highlights persistent DNS vulnerabilities threatening DeFi frontends.

Attack exploited social engineering on registrar Namecheap, exposing supply chain risks in crypto infrastructure.

Rapid response and compensation underscore industry push for stronger domain security and user safeguards.

How the Attack Unfolded

In a detailed incident disclosure posted on X, Across said the attack began at approximately 18:45 Coordinated Universal Time (UTC) on November 10. According to the team, a social engineering attack on Namecheap “gave a bad actor control of the Across domain.”

Social engineering means tricking people, such as a company’s support staff, into handing over access or making account changes, rather than breaking into technical systems. A domain registrar is the company that manages the registration of a website address. Control at the registrar level lets an attacker change where that address points, so visitors who type the correct URL can end up on a malicious copy of the site.

Across said it was alerted within 15 minutes and immediately began working to shut the website down. SEAL 911, the emergency response team of the Security Alliance (SEAL), marked across.to as a phishing site with major wallet providers. Cloudflare, a web infrastructure and security company, worked with Across to mark the domain as at risk. It later removed the site’s Domain Name System (DNS) records, which are the entries that tell browsers which server a domain points to. Removing them took the phishing page offline.

At around 19:05 UTC, Across issued its first public warning. It told users not to visit the app, connect a wallet, or sign any transaction or approval there until further notice.

Namecheap Initially Unresponsive

In its disclosure, published at around 22:13 UTC, Across said that “despite our best efforts, @Namecheap has been unresponsive.” The team said this left it unable to fully secure the domain and restore services. Across’s frontend, the website users interact with, and its application programming interface (API), which developers use to connect to the protocol, stayed offline during this period.

The team said its domain had been locked down with what it called best-in-class security practices, and that the “unauthorized takeover should not have been possible.”

Who Was Affected

According to Across, users who visited across.to in the short window before the malicious site was fully blocked may have been affected. API users and third-party integrations were not affected. Users who used the Across frontend only before the attack were also safe.

Across asked users who believe they were affected to contact the team by direct message on X. It also asked them to use Revoke.cash to revoke any permissions granted that day from the wallet they connected. These permissions, known as token approvals, allow a smart contract to move tokens out of a user’s wallet. Phishing sites often use them to drain funds.

Domain Restored, Compensation Pledged

At around 01:16 UTC on November 11, Across announced that the domain had been restored and that all systems were working normally again. The team credited Namecheap founder Richard Kirkendall with helping secure the account and said an investigation had been opened.

“All affected users will be made whole. We’ll share a full post-mortem in the coming days,” Across said. The team also said some wallets or browsers may still show phishing warnings for the domain for a short time.

Across has not yet disclosed the total value of funds lost or the number of affected users.

A Recurring Threat to DeFi Frontends

The incident is the latest attack on the web infrastructure behind decentralized finance (DeFi) platforms rather than on their smart contracts. In March, DeFi protocol Neutrl paused its smart contracts amid a suspected DNS frontend hijack and urged users to revoke wallet approvals. More broadly, crypto losses from hacks crossed $1.1 billion in the first half of 2026, according to blockchain security firm Blockaid.

Across has advised users to trust only its official channels and to ignore any other messages, links, or direct messages that claim to come from the team. A full post-mortem is expected in the coming days.

Also Read: Robinhood Chain DEX Arcus Loses $2.23M to Accounting Bug


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *