0x7f2680687f26…7f268065

ConfirmedSecurity598 vB150 sat/vB3 min decode

Curve Disables Fee Contract After $38,200 Exploit Drains 135 Tokens

Curve's emergency DAO disabled CowSwapBurner on Nov. 10 after an exploit converted balances from 135 tokens into 38,205 USDC. A replacement vote closes Nov. 20.

Curve Disables Fee Contract After About $38,200 in Fee Revenue Was Stolen
WitnessCurve Disables Fee Contract After About $38,200 in Fee Revenue Was Stolengeralt / pixabay

Outputs

  1. Emergency DAO disabled CowSwapBurner on Nov. 10 after roughly $38,200 in fee revenue was stolen

  2. Exploit converted small balances from 135 tokens into 38,205 USDC sent to an attacker-controlled address

  3. Flaw: contract verified the order displayed on CoW Protocol but not the order that executed

  4. User funds, liquidity pools, lending markets and crvUSD were unaffected; stolen funds not recovered

  5. DAO vote on a replacement contract is scheduled to close Nov. 20

Curve Finance's emergency DAO disabled the CowSwapBurner contract on Nov. 10 after the protocol attributed roughly $38,200 in stolen fee revenue to an exploit that converted small balances across 135 tokens into 38,205 USDC. A DAO vote on a replacement contract is scheduled to close Nov. 20.

The attack exploited a verification flaw. Curve's account explained the defect in precise terms: CowSwapBurner checked the order displayed on CoW Protocol but not the order that actually executed. An attacker used that gap to swap residual token balances held by the burner into USD Coin and route the proceeds to a controlled address.

The emergency DAO responded by pausing fee conversions on Ethereum entirely. The stolen funds had not been recovered as of the disclosure.

What does this change for Curve users?

For now, very little on the user side, and that distinction matters. Curve stated that the incident did not touch user funds, liquidity pools, lending markets or crvUSD. A routine conversion of 97,317 crvUSD completed as scheduled during the same week the exploit was identified.

The damage is confined to protocol fee revenue — the stream that accrues to the DAO and its recipients rather than to depositors. At approximately $38,200, the direct loss is modest by the standards of DeFi incidents, but the mechanism is the concern. A burner contract that validates what an order claims to be, rather than what it settles to, is a textbook oracle-of-execution gap, and any protocol routing fees through batch-auction settlement faces the same structural question.

Why the burner design failed

CowSwapBurner exists to convert accumulated trading fees in dozens of long-tail tokens into a single settlement asset before distribution. The contract's verification logic trusted the order as presented on CoW Protocol's interface layer. It did not independently confirm the executed outcome on-chain. That asymmetry between displayed intent and settled reality gave the attacker a window: present one order, execute another, and pocket the difference.

The scope — 135 distinct tokens, each drained of a small balance — indicates the attacker swept fragmented residue rather than targeting a concentrated position. That pattern is consistent with an opportunistic sweep of the burner's holdings rather than a targeted strike on a specific fee asset.

The operational path forward

Three steps define the recovery timeline:

  • Nov. 10: Emergency DAO disables CowSwapBurner and pauses fee conversions on Ethereum.
  • Ongoing: Stolen funds remain unrecovered; no repayment figure has been disclosed.
  • Nov. 20: DAO vote on a replacement contract closes, clearing the way to restore automated fee conversion.

Until the replacement passes and deploys, fee conversion on Ethereum stays offline. Fee revenue will accumulate in its native tokens rather than being swept into USDC, which adds accounting friction for the DAO and its distribution recipients but does not block trading, lending or stablecoin operations.

The practitioner's question

n What does this change for other protocols? Any project that routes fees, treasury sweeps or residual balances through CoW Protocol — or any batch-auction mechanism — should review whether its contracts verify executed settlements independently of the order data supplied by the settlement layer. Curve's incident demonstrates that the gap between displayed and executed orders is not theoretical, and that the cost of closing it is trivially small compared with even a five-figure loss plus the operational downtime of an emergency pause.

The Nov. 20 vote closes the immediate chapter. Whether the DAO pairs the new contract with independent execution verification will determine whether this remains a one-off sweep or a recurring surface for attackers.

via tokenpost.com (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,512 articles