How a 24-Second DeFi Hack Triggered a $100 Million Exit Nobody Talked About

 



A DeFi protocol lost $215,000 in under half a minute on May 27. That part made headlines. What followed did not.

Fluid, a lending and DEX protocol running on Ethereum, Base, and Arbitrum, had its off-chain Merkle reward distribution system drained by an attacker who held both of the keys required to propose and approve reward payouts. The hack itself was surgical. The proposer key submitted a fake reward root. The approver key signed off twelve seconds later. Twenty-four seconds after that, 112,883.85 FLUID tokens were gone. Then GHO. Then a small amount of cbBTC. All of it converted to roughly 142.6 ETH and routed into Tornado Cash.

The core protocol, smart contracts, user deposits, lending markets, vaults, DEX liquidity, none of it was touched. But the reward payout layer ran on infrastructure with no timelock, no dispute window, and no separation between the two signing roles.

The team removed the compromised keys about ten hours after the first theft and swept remaining reward balances to safety. They announced it publicly on May 31, four days after the exploit.

In those four days, on-chain data shows a $77 million USDC withdrawal from the protocol starting May 28. The team posted about high deposit rates that same day. The deposits kept leaving.

Pablo Veyrat, co-founder of Merkl, a competing Merkle distribution infrastructure provider, explained in a post on X exactly why the attack succeeded: no dispute window meant no reaction time. At Merkl, roots go through a minimum one-hour delay with three independent dispute bots scanning each new root for anomalies before claims become possible. Fluid's custom system had no equivalent.

The failure here was not the smart contract. It was the operational layer. Privileged keys with no independent custody, no delay between approval and claim, and no real-time outflow alerting. The result was a $215K loss in 24 seconds and a bank run that moved ten times more capital than the attacker took.

For full forensic breakdown and the detailed post-mortem of how the attack unfolded across all three chains, visit CryptoNewsLive.org.

Comments

Popular posts from this blog

Ripple Is Building XRPL's Defense Against Quantum Computing, and the Clock Is Already Running

Hoskinson Just Said Everything Nobody Else Will Say About Crypto in 2026

Everclear Is Gone and the $500M Volume Story Should Worry Every DeFi User