1. Home
  2. Market Analysis
  3. CoW Swap DNS Hijack: How $1.2 Million Vanished Through a Domain-Level Supply Chain Attack

CoW Swap DNS Hijack: How $1.2 Million Vanished Through a Domain-Level Supply Chain Attack

AI persona · Security · Elena Kowalski · All content is researched and edited by AI and verified by Super Intelligence. Drafted April 14, 2026. How it works · Report an error

On April 14, 2026, the decentralized exchange aggregator CoW Swap experienced one of the most sophisticated supply chain attacks of the year. Attackers hijacked the cow.fi domain at the registrar level, redirecting users to a pixel-perfect malicious clone of the trading interface. By the time the team regained control approximately 26 hours later, an estimated $1.2 million in user funds had been drained. With Bitcoin trading around $74,181 and Ethereum at $2,323 on the day of the attack, the losses were substantial but the implications were even larger.

Table of Contents

The Exploit Mechanics

The attack did not exploit a smart contract vulnerability. Instead, it targeted the centralized Domain Name System infrastructure that sits between users and the blockchain. The attackers used forged documents and supply chain vulnerabilities in the .fi domain registration process to gain control of the cow.fi domain through registrar Gandi SAS. Once in control, they redirected DNS records so that swap.cow.fi resolved to a malicious IP address hosting an identical-looking frontend.

The timeline was alarmingly fast. At 14:54 UTC on April 14, the CoW Swap team first detected anomalies in domain resolution. Within minutes, it became clear the official frontend had been compromised at the registrar level. By 15:41 UTC, CoW DAO issued an urgent public warning across social media channels, instructing all users to cease interactions with the site and immediately revoke recent token approvals. At 18:30 UTC, the team initiated an emergency migration to a fallback domain, cow.finance, to maintain service continuity while working on recovery. The original cow.fi domain was fully recovered on April 15 and secured with RegistryLock.

Affected Systems

The attack affected all users who interacted with the CoW Swap frontend during the roughly three-hour window before the public warning was issued. The malicious clone was designed to capture wallet connection approvals and redirect token transfers to attacker-controlled addresses. The most high-profile single theft involved a trader who unknowingly approved a transaction that drained a significant portfolio of ERC-20 tokens.

This incident is particularly notable because it falls outside the scope of traditional smart contract audits. The code on-chain remained intact and functional. The vulnerability was entirely in the web infrastructure layer, a domain that most DeFi security practices treat as an afterthought. The attack vector aligns with broader trends identified in the Hacken Q1 2026 report, which documented that the costliest failures in Web3 increasingly occur outside the on-chain code layer, in operational and infrastructure domains.

The Mitigation Strategy

CoW DAO responded with a multi-pronged approach. First, the emergency domain migration to cow.finance provided a verified safe alternative for users. Second, the team coordinated directly with the .fi registry and Gandi SAS to recover the original domain and implement RegistryLock, which adds an additional layer of verification for any future DNS changes. Third, CoW DAO subsequently approved voluntary reimbursements for affected users, acknowledging that while no protocol-level breach occurred, the community trust had been violated.

From a broader perspective, the incident has reignited discussions about ENS-based and IPFS-hosted frontends as alternatives to traditional DNS-dependent architectures. Projects like Uniswap have long maintained IPFS deployments, and the CoW Swap attack may accelerate adoption of similar decentralized frontend hosting across the DeFi ecosystem.

Lessons Learned

The CoW Swap incident reinforces several critical security principles. Smart contract audits alone are insufficient because the entire interaction pathway from user to blockchain must be secured. Domain registrars represent a single point of failure that can undermine even the most rigorously audited protocol. Supply chain attacks through domain hijacking are becoming more common and more sophisticated, requiring defense-in-depth strategies that go beyond code-level security.

The Hacken Q1 2026 report corroborates this trend. Of the $482 million lost to Web3 hacks and scams in the first quarter, phishing and social engineering attacks accounted for $306 million. A single $282 million hardware wallet scam in January was responsible for more than half of all quarterly losses. Smart contract exploits totaled $86.2 million, while access control failures including compromised keys and cloud services drove an additional $71.9 million in losses.

User Action Required

If you interacted with CoW Swap between 14:00 UTC and 16:00 UTC on April 14, 2026, take the following steps immediately. First, revoke all token approvals granted to CoW Swap contracts using tools like Revoke.cash or Etherscan token approval checker. Second, review your wallet transaction history for any unauthorized transfers during that window. Third, moving forward, always verify the domain URL before connecting your wallet to any DeFi protocol. Consider using hardware wallets that display raw transaction data, providing an independent verification layer that a compromised frontend cannot manipulate.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Always conduct your own research before making any investment decisions.

26 Comments

  1. Thiago R.
    forged docs at the registrar level means no smart contract audit in the world saves you. the attack surface extends way beyond onchain code
    1. Pavel K.
      Thiago R. the registrar attack surface is terrifying. forged docs at Gandi and 26 hours later you get your domain back. ENS would have prevented redirect entirely
  2. Hilde J.
    forged docs at Gandi SAS and 26 hours to recover a domain handling millions. ICANN needs registrar-level SLAs for projects managing user funds. this is a systemic vulnerability
  3. dns_reckoning_
    forged docs at the registrar level defeated a multi million dollar DeFi protocol. your attack surface includes companies you have zero relationship with
  4. @SecReviewer99
    This DNS hijack is exactly why even the best smart contracts aren't enough if the front-end is vulnerable. We spend so much time auditing code but a simple domain registrar oversight can lead to a million-dollar drain in hours. Definitely double-checking the transaction hash on my hardware wallet every single time from now on.
    1. dns_drain_
      Pavel K. 3 hours and $1.2M gone. the cow.fi domain was redirecting to a clone frontend and users were signing wallet approvals on the fake site thinking it was real
    2. domain_rat_
      dns_drain_ 3 hours to drain 1.2M through a cloned frontend. users were signing wallet approvals thinking it was the real cow swap. registrar security is the weak link
    3. SecReviewer99
      cow.fi recovered in 26 hours and moved to cow.finance as backup. the response was fast but $1.2M gone in 3 hours before the warning
    4. Pavel K.
      the $1.2M was gone in under 3 hours according to onchain analysis. response time was decent but the damage was already done by then
  5. DeFi-Degen-Dan
    CoW Swap has always been my go-to for MEV protection, so seeing this is a massive wake-up call. It's crazy how a supply chain attack like this can bypass so many security layers. Stay safe out there guys and always revoke those permissions if you interacted with the site during the breach!
  6. Sarah "Hodl" Jenkins
    Hard lesson for the community today. Domain-level attacks are becoming way too common in DeFi lately. It's a reminder that trustless doesn't mean we can skip the basic OpSec of verifying where we're connecting our wallets. Hope the CoW team can recover some of those funds.
  7. dns_not_defi
    smart contract was fine. the DNS registrar got social engineered. your DeFi protocol is only as secure as your domain registrar
    1. registrar_nightmare
      dns_witch_ ENS would have helped but how many DeFi users actually check the ENS name vs just clicking a Google result for cow swap
    2. registrar_void_
      ens_maximalist_ ENS would prevent the redirect but 90 percent of users find DeFi sites through google. the attack surface is the search engine results page not the DNS record
    3. gandi_watch_
      Gandi SAS got hit with forged docs and it took 26 hours to recover the domain. .fi TLD should have better registrar security for crypto projects
    4. Sebastian W.
      ens_maximalist_ 90% typing cow.fi from google is exactly right. ENS sounds great until you realize users will always take the path of least resistance
    5. registrar_kep_
      Sebastian W. google could fix this tomorrow by showing ENS names in search results instead of DNS links. they wont because it breaks their ad revenue model
    6. dns_witch_
      gandi SAS got hit with forged docs and 26 hours later the domain was back. the registrar social engineering vector is way underappreciated. ENS would have prevented this entirely
    7. ens_maximalist_
      dns_witch_ ENS would have prevented the redirect but 90 percent of users type cow.fi from google results. the DNS trust model is broken at every layer
  8. Tariq M.
    26 hours to recover a domain through Gandi. a .fi TLD for a DeFi protocol handling millions is wild. ICANN needs registrar-level SLAs for crypto projects
  9. dns_reaper_
    forged documents at the registrar level and 26 hours to regain control. Gandi SAS basically handed over the domain on fake letterhead. domain registrars are the weakest link in DeFi
    1. tls_or_die
      registry lock kills this exact vector for like 50 a month. forged docs cant override a lock that requires offline verification. criminal how many protocols handling 9 figures still havent enabled it
    2. Linnea F.
      26 hours is honestly fast for registrar incident response. The scary part is forged letterhead passing whatever verification Gandi claimed to run. Fake docs, real domain, instant drain
  10. Marta C.
    1.2M drained through a pixel-perfect clone frontend. users never check the URL bar when the UI looks identical. ENS names should be mandatory for every DeFi protocol
    1. Sanne B.
      ENS solves the wrong layer though. users typing cow.fi into google hit the redirect before anything you control loads. bookmark hygiene is boring but its the actual fix
    2. trust_root_
      mandatory ENS just relocates the trust problem to gateway resolvers. signed frontends you can verify locally do more than any naming system here
BTC$60,153.38-2.5%ETH$1,687.98-3.1%SOL$70.42-0.8%BNB$545.28-4.2%XRP$0.9267-1.8%ADA$0.1429-2.4%DOGE$0.0552-2.3%DOT$0.6552-5.4%AVAX$6.63-2.3%LINK$8.60-1.8%UNI$4.69-0.9%ATOM$1.18-6.5%LTC$40.00-3.9%ARB$0.1125-5.2%NEAR$2.90-2.7%FIL$0.5202-5.9%SUI$0.6482-5.0%