The Incident: A Brief Domain Takeover

Official reports confirm that on April 14, the domain registrar servicing CoW DAO fell victim to a sophisticated social engineering attack. Exploiting this breach, attackers gained control of the project's primary domain for a period of approximately four and a half hours. During this critical window, visitor traffic was redirected to meticulously crafted phishing sites.

The intent of these malicious platforms was clear: to deceive unsuspecting users into signing seemingly legitimate transactions that contained hidden, harmful permissions. The project team later clarified that the core CoW Protocol smart contracts and underlying infrastructure remained uncompromised. The risk was isolated entirely to individual users who interacted with the phishing sites during the domain's hijacking.

Community Action: A Discretionary Fund Established

In response, the CoW DAO community swiftly initiated its governance process. A key proposal, CIP-86, was put forward for community vote. Its central purpose was to approve the creation of a "Discretionary Compensation Fund" dedicated to reimbursing users who suffered verifiable financial losses during the incident.

Following broad community discussion and voting, CIP-86 has now officially passed. This moves the compensation mechanism from proposal to implementation, demonstrating the decentralized community's responsible approach to user asset security and its capacity to manage crises through collective governance.

User Guidance: Time-Sensitive Claim Process

With the compensation plan activated, the project has issued clear guidance for potentially affected users. Reimbursement is not automatic and requires eligible individuals to proactively file a claim.

  • Eligibility: Users who incurred asset losses after interacting with phishing sites and signing malicious transactions during the ~4.5-hour domain hijacking period on April 14.
  • Critical Deadline: All claims must be submitted through the official designated channels by May 14, 2024. Claims filed after this date will not be considered.
  • Recommended Action: Users should promptly review their transaction history for the relevant timeframe. If discrepancies are found, a detailed loss report with supporting evidence should be filed immediately via the official channels announced by the team.

This event serves as another stark reminder for the broader Web3 ecosystem, highlighting the need for constant vigilance against off-chain risks like domain security and social engineering attacks.