Press Enter to search · ESC to close

DeFi

Across Protocol Hit by DNS Hijack: Social Engineering Attack Compromises Domain, Users to Be Compensated

Cross-chain protocol Across suffered a domain hijack after its registrar Namecheap was socially engineered, leading to a phishing site. The team responded swiftly, and affected users will be compensated. The incident highlights the vulnerabilities of relying on centralized domain services in DeFi.

Cross-Chain Protocol Across Suffers Domain Hijack

Cross-chain protocol Across revealed that its domain registrar, Namecheap, fell victim to a social engineering attack on November 11 at around 02:45 UTC, allowing attackers to gain control of the Across domain. The team was alerted within 15 minutes and immediately began shutting down the website. The phishing site, across.to, was flagged by SEAL911 and Cloudflare subsequently revoked the DNS records, making the site inaccessible.

Some users who visited across.to before the takedown may have been affected, though third-party integrations and API users were not impacted. Across has committed to compensating all affected users and advises them to revoke any related approvals via revoke.cash. The frontend and API will remain offline until domain security is fully restored.

Industry Analysis: The Rising Threat of Social Engineering

This incident underscores the growing sophistication of social engineering attacks targeting crypto infrastructure. Domain registrars, often seen as peripheral to blockchain security, are becoming a weak link. Attackers can bypass decentralized protocol safeguards by exploiting centralized points of failure, such as domain registration systems.

The swift response by Across and the involvement of security firms like SEAL911 and Cloudflare highlight the importance of rapid incident response. However, the attack also raises questions about the reliance on traditional DNS systems in DeFi. While blockchain transactions are immutable, the user interface layer remains vulnerable to hijacking, exposing users to phishing risks.

Implications for DeFi Security

  • Centralized Vulnerabilities: Even decentralized protocols depend on centralized services like domain registrars, creating potential attack vectors.
  • User Education: Users must remain vigilant and verify URLs, especially after security alerts. Tools like revoke.cash are essential for managing token approvals.
  • Compensation and Trust: Across’s commitment to compensate affected users helps maintain trust, but the incident may prompt a broader review of security practices across the industry.

Forward-Looking Perspective

As DeFi continues to mature, security must extend beyond smart contracts to encompass the entire user journey, including domain management and frontend security. Projects may increasingly adopt decentralized domain services (like ENS) or multi-factor authentication for registrar accounts. Regulators and industry bodies could also push for stricter security standards for service providers. While this attack was contained, it serves as a wake-up call for the crypto industry to address off-chain vulnerabilities that can have on-chain consequences.

Share
Risk notice News, market information, data and other content published by 新云社 are for information and general reference only, and do not constitute investment, legal, tax or other professional advice.

Related Reading

Latest News

新云社 share card
Long-press image above → Save to Photos / Share
Pitch us Feedback