The $292 Million Kelp DAO Breach Highlights the Vulnerability of Crypto Bridges

The recent $292 million breach linked to KelpDAO is the latest in a string of crypto bridge hacks, emphasizing the vulnerabilities of the systems designed to connect blockchains. This incident involved KelpDAO's use of LayerZero's cross-chain messaging system, a type of infrastructure commonly used for transferring data and assets between blockchains. Bridges are intended to facilitate the movement of assets between different blockchains, such as from Ethereum to another network. However, instead of serving as secure connectors, they have consistently proven to be weak points, resulting in the loss of billions of dollars over the past few years. According to crypto ecosystem leaders, the problem is not merely a result of poor coding or careless mistakes, but rather a fundamental issue with the way bridges are constructed. At the core of the problem is the reliance on intermediaries. When transferring tokens from one blockchain to another, the second chain requires verification that the tokens existed and were locked on the first chain. Ideally, it would verify this information independently, but in reality, this process is too complex and expensive. Most bridges do not fully verify the transactions on the other chain and instead rely on a smaller system to report the information, which becomes the trusted source. This approach creates a vulnerability, as seen in the Kelp DAO-related exploit, where attackers targeted the data feeding into the bridge. Experts argue that bridge hacks often manifest differently on the surface, with some involving stolen keys and others involving faulty smart contracts, but these are symptoms of a deeper design issue. The true problem lies in the way these systems are designed, with a mix of code vulnerabilities, centralization issues, social engineering, and economic attacks. For users, bridges appear simple, but the process behind the scenes is more complicated. The tokens are first locked on the original blockchain, and then a separate system confirms the lock. This system typically consists of a small group of operators or validators who send a message to the second blockchain to issue new tokens. The issue arises when this process relies on trusting the sender of the message, and if attackers compromise this system, they can send false messages and create unbacked tokens. Given the frequency of bridge failures, it is surprising that the industry has not yet addressed these issues. Part of the reason lies in the incentives, with security often not being the top priority for teams focused on quick launches, user growth, and increasing total value locked. Building secure systems requires time and money, which many DeFi projects lack, making it challenging to invest in audits, monitoring, and infrastructure. The addition of new blockchain integrations further complicates the issue, introducing more assumptions and potential vulnerabilities. Bridge hacks can have far-reaching consequences, as compromised assets are used across lending protocols, liquidity pools, and yield strategies, leading to contagion. Users are often unaware of how bridges work and the potential risks involved. To improve bridge safety, experts recommend removing single points of failure by relying on independent data sources rather than shared infrastructure. This can involve using computers that watch blockchains and report on transactions, which can be run by the bridge itself or external networks. However, many of these sources rely on the same underlying services, meaning a single compromised source can feed bad data across multiple systems. Other approaches include hardware protections, better monitoring, and designs that verify data directly using cryptography instead of intermediaries. Ultimately, a more fundamental shift is needed to address the vulnerabilities of crypto bridges.