Bitget's affected asset scale was revised up to $388 million, while KelpDAO sued LayerZero and its CEO over a $292 million rsETH cross-chain bridge theft. The two incidents involve combined assets of about $680 million, focusing industry attention on centralized exchange risk controls and cross-chain bridge security and liability allocation.
Two security incidents involving relatively large amounts have occurred in quick succession in the crypto industry. First, the scale of assets affected by the Bitget security incident has been revised up to $388 million, $35 million more than previously disclosed. Second, KelpDAO has filed a lawsuit against LayerZero and its CEO over the $292 million rsETH cross-chain bridge theft. The two incidents involve combined assets of about $680 million and point to two types of risk scenarios, centralized exchanges and cross-chain infrastructure, making exchange risk controls, cross-chain bridge security and liability allocation key industry concerns.
Bitget Incident's Affected Assets Revised Up to $388 Million
According to disclosures, the scale of assets affected by the Bitget security incident has been revised up from previously public figures to $388 million, an increase of $35 million. Based on the revised figure, the previously disclosed scale of impact was approximately $353 million. The upward revision itself indicates that related verification and accounting work is still ongoing, and the scope of affected assets expanded during subsequent investigations, with incident information in a process of dynamic updating.
For centralized exchanges, security incidents directly affect the custody and withdrawal of user assets and also test platforms' risk control systems, asset segregation arrangements and emergency response capabilities. The upward revision of the affected asset scale makes this incident one of the higher-value cases in recent exchange security issues. The source material shows that the incident involves user assets and exchange risk controls, and market attention to exchanges' security capabilities has risen accordingly. After the upward revision, the incident's impact boundary, the handling of user assets and the platform's follow-up explanations have all become subjects of continued external observation.
KelpDAO Sues LayerZero and CEO Over rsETH Cross-Chain Bridge Theft
Another main thread comes from the DeFi sector. KelpDAO has filed a lawsuit over the $292 million rsETH cross-chain bridge theft, with defendants including LayerZero and its CEO. The case revolves around the cross-chain bridge vulnerability itself and the liability of relevant protocol parties, with the core dispute being the attribution of responsibility for the $292 million theft. As an asset in cross-chain scenarios, the theft of rsETH directly hit the fund security of the cross-chain bridge.
Unlike the risk form of centralized exchanges, cross-chain bridges connect asset flows across multiple chains. Once a vulnerability appears, risk may be transmitted along cross-chain paths. This lawsuit extends the technical vulnerability issue to the legal liability level, making the security liability boundary of cross-chain infrastructure a focus of industry discussion. The source material shows that the incident involves a $292 million cross-chain bridge vulnerability and a dispute over LayerZero's liability, and DeFi security and legal risks have drawn high attention. The advancement of the lawsuit means that incident handling has moved from the technical investigation stage to the liability determination stage, which usually requires a longer cycle.
Both Incidents Point to Infrastructure Security
From the perspective of risk type, the two incidents occurred respectively in two segments, centralized exchanges and cross-chain bridges, but both point to the same issue: crypto asset infrastructure still has risk exposures in key segments such as asset custody and cross-chain transmission. The keywords of the Bitget incident are affected asset scale and exchange risk controls; the keywords of the KelpDAO incident are cross-chain bridge vulnerability and liability dispute.
What the two have in common is that the final impact of the incidents was not fully clear at the outset. The former's amount was revised up in subsequent disclosures, indicating that confirmation of the loss or impact scale requires a continuous verification process; the latter has entered the litigation stage, liability determination is still pending, and the liability boundaries of relevant parties remain to be clarified. The impact of such incidents is reflected not only at the direct funding level, but also in users' and institutions' reassessment of platform security capabilities and the reliability of cross-chain solutions. The disclosure standards, handling progress and liability allocation of security incidents are becoming important observation dimensions for measuring relevant projects and platforms.
At the industry level, the two incidents involve combined assets of about $680 million, a relatively large scale, making exchange security and cross-chain bridge security public issues again. For centralized platforms, how to promptly and accurately disclose the scope of impact after an incident and update information during verification is a key market concern; for DeFi and cross-chain projects, liability attribution and legal pathways after vulnerabilities occur also need clearer rule support.
Follow-Up Focus
As for the Bitget incident, follow-up attention should be paid to whether the scale of affected assets will change further, and to the platform's progress and explanations regarding the handling of user assets. As for the lawsuit between KelpDAO and LayerZero, follow-up attention should be paid to the case's progress in liability determination and the possible impact of the case on the allocation of cross-chain bridge security liability.
From an industry perspective, the two incidents involve combined assets of about $680 million and combine the two issues of exchange risk controls and cross-chain bridge security. The verification results, judicial progress and handling plans of the relevant incidents will be important clues for observing the direction of industry security governance.
.jpg)
