North Korea's Expanding Crypto Theft Strategy Hits DeFi with Over $500 Million in Losses

Less than three weeks after North Korea-linked hackers compromised crypto trading firm Drift using social engineering tactics, another major exploit has been attributed to hackers tied to the nation, this time targeting Kelp, a restaking protocol connected to LayerZero's cross-chain infrastructure. This attack signifies an evolution in the tactics employed by North Korea-linked hackers, who are no longer just exploiting bugs or using stolen credentials but are now manipulating the fundamental assumptions underlying decentralized systems. The cumulative effect of these incidents suggests a more coordinated effort by North Korea to hijack funds from the cryptocurrency sector. According to Alexander Urbelis, chief information security officer and general counsel at ENS Labs, 'This is not a series of incidents; it is a cadence. You cannot patch your way out of a procurement schedule.' The Drift and Kelp exploits collectively resulted in the theft of over $500 million in just over two weeks. The Kelp breach did not involve breaking encryption or cracking keys; instead, attackers manipulated the data feeding into the system, forcing it to rely on compromised inputs and thus approving transactions that never occurred. As Urbelis noted, 'The security failure is simple: a signed lie is still a lie. Signatures guarantee authorship; they do not guarantee truth.' This exploit highlights a security failure not due to a sophisticated hack but rather the exploitation of how the system was configured. David Schwed, COO of blockchain security firm SVRN, pointed out, 'This attack wasn’t about breaking cryptography. It was about exploiting how the system was set up.' A key issue was the configuration choice to rely on a single verifier to approve cross-chain messages, a decision made for speed and simplicity but one that removes a critical safety layer. Following the exploit, LayerZero recommended using multiple independent verifiers to approve transactions, akin to requiring multiple signatures on a bank transfer. However, some have pushed back, stating that LayerZero’s default setup was to use a single verifier. Schwed argued, 'If you’ve identified a configuration as unsafe, don’t ship it as an option. Security that depends on everyone reading the docs and getting it right is not realistic.' The impact of the exploit has not been contained to Kelp, as its assets are used across multiple platforms, leading to a wider stress event. Lending platforms like Aave, which accepted the impacted assets as collateral, are now dealing with losses. The gap between the marketing of decentralization and its actual implementation has been exposed by this attack. Schwed stated, 'A single verifier is not decentralized. It’s a centralized decentralized verifier.' Urbelis expanded on this, saying, 'Decentralization is not a property a system has. It is a series of choices. And the stack is only as strong as its most centralized layer.' In practice, this means that even seemingly decentralized systems can have weak points, particularly in less visible layers such as data providers or infrastructure, which are increasingly the focus of attackers. The recent targeting by Lazarus, a group linked to North Korea, of cross-chain and restaking infrastructure—critical but complex layers that move assets between systems or allow them to be reused—highlights this shift. These layers are not only crucial but also hold large amounts of value, making them attractive targets. If earlier crypto hacks focused on exchanges or obvious code flaws, recent activity suggests a move toward targeting the industry’s underlying infrastructure, the systems that connect everything together but are harder to monitor and easier to misconfigure. As Lazarus adapts, the biggest risk may not be unknown vulnerabilities but known ones that are not fully addressed. The Kelp exploit did not introduce a new kind of weakness but showed how exposed the ecosystem remains to familiar ones, especially when security is treated as a recommendation rather than a requirement. This gap is becoming both easier to exploit and far more expensive to ignore.