Lazarus Group Blamed for $522M in Twin Strikes on Circle and KelpDAO
North Korean state-sponsored hackers stole $522M from Circle and KelpDAO in back-to-back attacks attributed to the Lazarus Group, exposing critical weaknesses in platform security and cross-chain messaging infrastructure.
Lazarus Group Blamed for $522M in Twin Strikes on Circle and KelpDAO
North Korean state-sponsored hackers stole a combined $522M from two cryptocurrency platforms in rapid succession, targeting Circle through an operational security failure and KelpDAO through a deep technical exploit of cross-chain infrastructure. Both attacks are attributed to the Lazarus Group, the same collective responsible for some of the largest crypto thefts on record.
Two Attacks, One Playbook
The first breach cost Circle $230M. According to Crypto Briefing, Circle's delayed response to an active security incident gave attackers the window they needed to complete the theft. The specific nature of the delay has not been fully disclosed, but the implication is clear: faster incident response could have limited or prevented the loss. For a company that positions itself as a regulated, institutional-grade stablecoin issuer, the breach raises hard questions about operational security and internal alerting protocols.
The second attack targeted KelpDAO, a liquid restaking protocol built around rsETH. Blockonomi reported that Lazarus Group exploited flaws in the DVN (Decentralized Validator Network) infrastructure underpinning LayerZero's cross-chain messaging system. DVNs are the verification layer that cross-chain protocols use to confirm that a message sent from one blockchain is legitimate before it is executed on another. Compromising that layer means an attacker can forge cross-chain instructions, effectively minting or moving assets without authorization. The KelpDAO breach resulted in $292M in losses.
Cross-Chain Bridges Remain the Weakest Link
The KelpDAO exploit fits a well-established pattern. Cross-chain bridges and messaging layers have been the single most lucrative attack surface in crypto for three consecutive years. Ronin Network lost $625M in March 2022. Poly Network was drained of $611M in 2021. Wormhole lost $320M in February 2022. Each of these incidents involved some form of validator compromise or message verification failure, precisely the category of vulnerability Lazarus exploited in the LayerZero DVN.
What makes this attack particularly notable is its target precision. Rather than attacking KelpDAO's smart contracts directly, the hackers went one layer deeper and targeted the messaging infrastructure that KelpDAO depends on. This upstream approach is harder to defend against because the exploited component sits outside the direct control of the protocol being drained. LayerZero has attributed the breach to DVN infrastructure flaws, a framing that distributes responsibility across the validation network rather than centering it on any single party.
That framing is contested. Cross-chain protocol teams frequently argue that security is a shared responsibility between developers, validators, and users. Critics counter that end users have no practical ability to audit DVN security, and that protocols marketing themselves as secure bear primary responsibility when that security fails.
Lazarus Group's Expanding Crypto Campaign
The Lazarus Group is not a peripheral threat actor. It operates as a division of North Korea's Reconnaissance General Bureau, under state direction to generate hard currency that bypasses international sanctions. The United Nations and multiple national governments have documented the group's systematic targeting of crypto platforms since at least 2017. Chainalysis estimated that North Korean hackers stole approximately $1.7B in cryptocurrency in 2022 alone, a figure representing a significant portion of the country's total foreign currency earnings.
The $522M taken in these two incidents would rank among the largest single-year hauls attributed to the group if confirmed. The combination of an operational security failure at Circle with a deep technical exploit at KelpDAO suggests Lazarus is running parallel attack tracks simultaneously: one targeting human and procedural weaknesses, the other targeting protocol architecture.
Regulatory Pressure Will Follow
Incidents of this scale do not pass without a regulatory response. The 2022 Ronin hack triggered Treasury Department sanctions against the Tornado Cash mixer and accelerated interagency discussions about crypto security standards. The 2021 Poly Network exploit contributed to the SEC and CFTC sharpening their focus on DeFi platform liability.
These two breaches will likely produce similar pressure. Circle, as the issuer of USDC and a company that has actively courted regulatory legitimacy, faces particular scrutiny. A $230M theft enabled in part by delayed incident response is difficult to explain to regulators who have been pushing for institutional-grade custody and security standards.
On the DeFi side, the KelpDAO breach will add ammunition to arguments that cross-chain interoperability protocols need mandatory security audits and possibly registration requirements before they can operate at scale. Industry advocates will push back, arguing that prescriptive regulation would freeze development of a technology still finding its architecture. That debate is legitimate, but it will be happening against the backdrop of $522M in confirmed losses tied to a foreign state actor.
The more durable fix is technical and organizational, not regulatory. Cross-chain messaging systems need multi-layered DVN verification with economic penalties severe enough to make validator collusion economically irrational. Platforms like Circle need incident response protocols that trigger automatic circuit breakers rather than human escalation chains that can stall under pressure.
Lazarus Group has demonstrated, repeatedly and at scale, that it treats the crypto sector as a revenue stream. The sector's response so far has been reactive. Each major exploit produces post-mortems, audits, and promises of improved security, followed by the next exploit. At $522M in a single campaign, the cost of that cycle is no longer abstract.



