Twelve smart contract audits passed, twelve DNS records stolen, and $138,000 gone in a day.

The Summary

The Signal

The attack worked like this: users visited what appeared to be legitimate DeFi protocol websites. They connected their wallets. They approved transactions. Except they weren't talking to the real protocol at all. The DNS records had been hijacked, redirecting traffic to attacker-controlled sites that looked identical to the originals.

Registry records show all 12 hijacked domains registered through Name.com, pointing to a compromise at the registrar level. This isn't a case of 12 projects making the same security mistake. One weak point, 12 entry doors.

"DNS vulnerabilities can undermine even flawless smart contracts."

The irony here is thick. DeFi projects spend months on smart contract audits. They run bug bounties. They build in time locks and multi-sig controls. Then they lose user funds because someone got into their domain registrar account. The decentralized protocol stayed secure. The centralized door to it did not.

This follows a pattern we've seen before:

  • Compound Finance's domain hijacked in 2022
  • Curve Finance DNS attack in 2023 that drained $570,000
  • Celer Network bridge interface compromise in 2024

The fundamental problem: you can build the most trustless protocol in the world, but if users reach it through a Web2 domain name system, you've got a single point of failure. The blockchain doesn't care what website sent the transaction. It just sees a wallet signature.

For users, the attack is nearly undetectable. The URL looks right. The site looks right. Maybe the SSL certificate warning pops up, but most people click through those. By the time you realize something's wrong, you've already approved a transaction draining your wallet to an attacker's address.

The Implication

If you're building in DeFi, your domain security matters as much as your smart contract security. Two-factor authentication on your registrar account isn't optional. Consider ENS or another blockchain-based naming system as your canonical address. Make your contract addresses the source of truth, not your .com.

If you're a user, verify contract addresses independently before approving transactions. Bookmark the real protocol URLs. Check the contract address against multiple sources, not just the website in front of you. The blockchain is trustless. The path you take to reach it is not.

Sources

Crypto Briefing | The Block