Ethlimo, an ENS-to-web gateway, has published a detailed report on a DNS hijacking incident that took place on Friday night. According to the disclosure, the breach was traced back to a social engineering attack targeting domain registrar EasyDNS, raising fresh concerns about how Web3-facing services can still be disrupted through traditional internet infrastructure.
A DNS hijack can redirect users attempting to visit a legitimate domain to an unauthorized destination. For a service operating as an ENS gateway, that kind of disruption can undermine both accessibility and trust, especially for users who rely on standard web access rather than interacting directly through decentralized tools.
Attack Path Led to the Registrar Layer
Ethlimo said the incident was not presented as a conventional exploit of its own platform, but instead was linked to the external domain management layer. The investigation found that the root cause was a social engineering attack against EasyDNS. In such attacks, threat actors typically manipulate human processes rather than defeating systems through purely technical means.
EasyDNS acknowledged the incident and described it as the first successful social engineering attack against a customer in its 28-year history. That statement underscores a broader industry reality: even long-established infrastructure providers remain exposed to risks created by human workflows and support channels.
Broader Lessons for Web3 Infrastructure
The episode highlights a persistent weakness across crypto and Web3 services. Even when an application is built around decentralized naming or identity systems, access points such as websites, DNS records, and registrar accounts may still depend on centralized intermediaries. If those layers are compromised, users can face service disruption or be routed to unsafe destinations.
With Ethlimo and EasyDNS now having publicly addressed the incident, the case serves as a warning for ENS-related projects and other crypto platforms that rely on DNS. Technical hardening remains important, but so do stronger safeguards around identity verification, account changes, and customer support procedures that can be exploited through social engineering.