The attack vector wasn't a smart contract exploit or a Discord phishing link — it was the domain registrar itself.

The Summary

  • At least 12 DeFi front-end sites were hijacked through compromised domains at registrar Name.com, with the StepDrainer malware redirecting users to wallet-draining sites
  • LaunchOnSF restored its website after being among the first victims, while the attack spread to 10 additional platforms
  • The breach exposed DeFi's Achilles heel: billion-dollar protocols built on Web3 rails still depend on Web2 infrastructure controlled by centralized gatekeepers

The Signal

Name.com, a domain registrar managing DeFi protocol URLs, suffered a breach that let attackers hijack at least 12 front-end domains. Users visiting these sites were redirected to StepDrainer malware pages designed to drain connected wallets. LaunchOnSF was hit early, went dark, then came back online as Name.com worked to restore control.

The irony cuts deep. DeFi exists to eliminate middlemen and trusted third parties. Your keys, your crypto. Code is law. Except when someone compromises the DNS registrar that points users to your supposedly decentralized protocol, none of that matters. The blockchain layer stayed perfectly secure while users got robbed at the front door.

"DeFi's reliance on traditional internet infrastructure" just cost real people real money, and the attack surface had nothing to do with Solidity or Move.

This wasn't a novel exploit. Domain hijacking is old-school internet crime. What's new is the target set. DeFi protocols are high-value honeypots with users trained to connect wallets fast. StepDrainer, a known wallet-draining kit, capitalized on that muscle memory:

  • User visits familiar URL (actually hijacked domain)
  • Site looks legitimate enough under time pressure
  • Wallet connection approval seems routine
  • Funds drain before user realizes the redirect

The 12-site spread suggests either a coordinated attack on multiple Name.com-hosted domains or a systematic breach of the registrar's control panel. Name.com restored the domains, but the window of exposure did damage. We don't have loss figures yet, but StepDrainer campaigns typically target high-value wallets and have historically netted six-figure hauls per attack wave.

The Implication

If you're building a DeFi protocol, your domain registrar is part of your attack surface now. Two-factor authentication on your DNS controls. Registry lock on your domain. Consider ENS or Handshake as backup resolution paths that don't route through ICANN-controlled chokepoints. The domain layer is centralized infrastructure masquerading as neutral ground.

For users: bookmark the actual contract addresses and verify them independently. IPFS gateways. ENS resolution. Anything that doesn't make Name.com a single point of failure between you and your assets. Web3 can't route through Web2 gatekeepers forever without inheriting Web2 vulnerabilities. This attack just proved it at scale.

Sources

Crypto Briefing | Crypto Briefing