North Korea's Cryptocurrency Theft Tactics Are Evolving, with DeFi Being Repeatedly Targeted

Less than three weeks after hackers linked to North Korea used social engineering to breach the cryptocurrency trading firm Drift, another significant exploit has been attributed to the nation, this time targeting Kelp, a restaking protocol connected to LayerZero's cross-chain infrastructure. This attack signals an evolution in North Korea-linked hackers' strategies, moving beyond exploiting bugs or stolen credentials to manipulating the fundamental assumptions underlying decentralized systems. The combined incidents of the Drift and Kelp exploits, which together resulted in the theft of over $500 million in just over two weeks, suggest a more organized effort by North Korea to hijack cryptocurrency funds. 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 Kelp exploit did not involve breaking encryption or cracking keys but rather manipulating the data input into the system, forcing it to rely on compromised inputs and approve transactions that did not occur. 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 that the system's security failure lies in its design, specifically in checking the sender's identity but not verifying the message's accuracy. David Schwed, COO of blockchain security firm SVRN, emphasized that the attack was not about breaking cryptography but about exploiting the system's setup, particularly its reliance on a single verifier for cross-chain messages. This configuration choice, while faster and simpler, removes a critical safety layer. In response, LayerZero has recommended using multiple independent verifiers to approve transactions, akin to requiring multiple signatures on a bank transfer. However, some have pushed back against this recommendation, arguing 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 Kelp exploit has not been limited to Kelp itself, as its assets are utilized 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. This situation underscores the interconnected nature of DeFi systems, where assets are essentially a chain of IOUs, and the chain is only as strong as the controls on each link. When one link breaks, others are affected. The exploit also reveals a gap between the marketing of decentralization and its actual implementation. As Schwed pointed out, 'A single verifier is not decentralized. It's a centralized decentralized verifier.' Urbelis expands on this, stating, '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, especially in less visible layers such as data providers or infrastructure, which are increasingly the focus of attackers. This shift may explain why Lazarus, a group linked to North Korea, has begun targeting cross-chain and restaking infrastructure, the parts of the crypto ecosystem that move assets between systems or allow them to be reused. These layers are critical but complex and often sit underneath more visible applications, holding large amounts of value and 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 continues to adapt, 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. And as attackers move faster, this gap is becoming both easier to exploit and far more expensive to ignore.