DeFi exploit pushes banks to reassess tokenization

TLDR

A large exploit of Kelp DAOs DeFi bridge is making banks and analysts slow down and re?examine how they use blockchains for tokenization.

1. Attackers minted about $290293 million of unbacked rsETH via Kelp DAOs LayerZero bridge, causing bad debt on Aave and a multibillion dollar DeFi liquidity run.
2. Jefferies told clients the incident could prompt big banks to pause or slow some blockchain and tokenization projects while they reassess infrastructure risks, especially cross?chain bridges and single?validator setups.
3. Tokenization is not dead, but the bar is rising: banks are likely to demand multi?issuer, multi?bank designs, stronger security standards, and clearer regulation before scaling on?chain assets.

Deep Dive

1. What Happened In The Exploit

Kelp DAOs rsETH bridge, built on LayerZero, was configured with a single verifier, creating a critical point of failure.

An attacker compromised that setup and spoofed a burn message, minting about 116,500 unbacked rsETH, roughly $290293 million, on Ethereum and depositing it into lending protocols like Aave as collateral, which left Aave with hundreds of millions in bad debt and pushed its markets to near 100 percent utilization, trapping user liquidity.

Across DeFi, total value locked fell by an estimated 913 billion dollars within days as users pulled funds, making this one of 2026s largest and most systemically visible DeFi failures.

2. How Banks Are Reacting

Jefferies warned that the Kelp DAO exploit, allegedly tied to North Koreas Lazarus Group, may cause Wall Street firms to slow the pace of some blockchain and tokenization efforts while they review security assumptions around bridges and custody.

The analyst note stresses that many tokenization pilots rely on similar cross?chain infrastructure and that single?validator or highly centralized components make decentralized systems vulnerable to the kind of cascading failure seen in Aave and related protocols.

At the same time, banks have already committed significant resources to tokenized money and assets, so the likely shift is toward stricter risk reviews and vendor standards rather than abandoning tokenization outright.

3. Tokenization Path From Here

Even as exploits mount, banks and corporates are still building tokenization rails, but they want them to look more like regulated market infrastructure than DeFi experiments.

Corporate treasury groups are publishing principles that stress multi?bank architectures, interoperability, strong controls, and clear legal finality for tokenized cash and deposits, signalling that tokenization must meet existing treasury standards, not bypass them.

In parallel, consortia of European banks are developing regulated euro stablecoins and tokenized cash instruments for settlement and tokenized assets, showing that bank?grade tokenization continues but with more emphasis on compliance and operational resilience than on DeFi?style yield.

Conclusion

The Kelp DAO exploit exposed how fragile cross?chain DeFi plumbing can be and showed banks what can go wrong when critical components are centralized or poorly governed.

Rather than killing tokenization, it is more likely to push banks toward slower, more conservative designs that favor regulated stablecoins, tokenized deposits, and tightly controlled infrastructure over open DeFi integrations, at least until security practices visibly mature.