Fluid Protocol, a decentralized finance lending platform formerly known as Instadapp, suffered a security breach on May 27 when a compromised key allowed attackers to drain approximately 125,000 FLUID tokens and 51,900 GHO tokens from its Merkle rewards distribution system. The exploit remained undisclosed for four days until on-chain researcher YAM publicly surfaced the incident on May 31, raising questions about the timeline between internal discovery and public notification.

What Happened in the Fluid Protocol Exploit?

The attacker, operating from wallet 0x4925120CbE5A78Bf08F26f6E8cdF820f4c1D3dfB, exploited a compromised key in Fluid's off-chain Merkle rewards infrastructure. The Merkle system is a technical mechanism that allows protocols to distribute rewards efficiently without storing all transaction data on-chain. In this case, the attacker used empty-proof Merkle claims to fraudulently claim rewards from multiple Fluid distributor contracts.

The timeline of the attack was remarkably tight. A proposer submitted a Merkle root, an approver approved it, and the exploiter claimed FLUID tokens roughly 24 seconds after the proposal went through. The GHO claim followed minutes later. After obtaining both token types, the attacker swapped the stolen assets and funneled proceeds through Tornado Cash, a privacy mixer commonly used to obscure the origin of stolen cryptocurrency.

Why Did Disclosure Take Four Days?

The gap between the May 27 exploit and the May 31 public disclosure has drawn sharp criticism from the crypto community. On-chain researcher YAM highlighted that Fluid only acknowledged the incident after independent analysis brought it to light, not through a proactive disclosure from the protocol team. YAM noted that a $77 million USDC withdrawal began on May 28, one day after the exploit, and that Fluid simultaneously promoted high USDC deposit rates, fueling suspicion that certain parties may have had advance knowledge before retail users were informed.

"The exploit was on May 27th. This exploit was surfaced earlier today (May 31st) and only after that was it disclosed. Why was it only disclosed now?" noted YAM in a reply to Fluid's official statement.

YAM, On-Chain Researcher

Fluid's official response on May 31 emphasized that the core protocol remains fully secure and that all smart contracts are safe and unaffected. The team stated that the impacted contract was not part of core protocol infrastructure and was used solely for rewards distribution with minimal funds in its balance. However, the protocol's statement notably omitted any mention of a key compromise or the specific amount of funds lost.

How Does This Reflect Broader DeFi Security Challenges?

The Fluid exploit highlights a recurring vulnerability across decentralized finance: the security of privileged keys and the operational trust layers that sit outside of smart contracts themselves. While Fluid's core smart contracts remained technically sound, the off-chain infrastructure managing rewards distribution proved to be a critical weak point. This distinction is important because it reveals that DeFi security extends far beyond code audits and smart contract verification.

The 2026 calendar year has been particularly brutal for DeFi security. According to industry data, crypto exploits and hacks have exceeded $770 million in total losses this year, with April alone recording over $635 million across 28 separate incidents. High-profile breaches at Drift Protocol ($285 million), Kelp DAO ($292 million), and THORChain ($10.8 million) have dominated headlines. The Fluid breach, while smaller in scale, adds to an alarming trend of vulnerabilities being discovered and exploited at an accelerating pace.

Steps to Understand Off-Chain Infrastructure Risks in DeFi

• Merkle Trees and Rewards Distribution: Many DeFi protocols use Merkle trees to efficiently distribute rewards without storing every transaction on-chain. This off-chain infrastructure requires trusted keys and approval processes, creating a potential attack surface if those keys are compromised or if the approval workflow lacks sufficient security controls.
• Key Management and Operational Security: Even when smart contracts are audited and secure, the keys that control administrative functions like proposing and approving Merkle roots must be protected with the same rigor as the contracts themselves. A single compromised key can enable an attacker to bypass all on-chain safeguards.
• Disclosure Timing and Community Trust: The delay between exploit discovery and public disclosure can erode user confidence in a protocol. Transparent and timely communication about security incidents is essential for maintaining trust, especially when large withdrawals or unusual activity might signal internal awareness of a problem.
• Layered Security Beyond Smart Contracts: DeFi security requires attention to multiple layers: smart contract code, key management, approval workflows, monitoring systems, and incident response procedures. A vulnerability in any single layer can compromise the entire system.

Fluid had previously demonstrated financial resilience in March 2026 when it repaid $70 million in bad debt from the Resolv Protocol exploit, a move that was widely praised by the community. However, the current incident suggests that operational security and key management may require as much attention as financial reserves.

The protocol announced that Merkle reward claiming would be temporarily paused for a few days, potentially up to a week, while updates are made. Rewards will continue accumulating retroactively, and claiming will resume once updates are complete. Fluid also confirmed that several hours after the exploit, an admin-style batched transaction removed the old proposer and approver roles across multiple Fluid rewards contracts, indicating that compromised keys were being rotated out.

The Fluid incident serves as a stark reminder that off-chain infrastructure and key management remain critical weak points in DeFi, even when core smart contracts are technically sound. As the industry continues to scale and protocols become more complex, the security perimeter extends far beyond what can be verified through code audits alone. The crypto community will be watching closely for Fluid's detailed post-mortem disclosure and any further developments regarding the drained funds and their potential recovery.