North Korea's Cryptocurrency Theft Tactics Are Evolving, with DeFi Being a Prime Target
Less than three weeks after hackers linked to North Korea used social engineering to breach the crypto trading firm Drift, another major exploit has been attributed 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 stolen credentials but are now manipulating the fundamental assumptions underlying decentralized systems. The combined impact of these incidents points to a more organized effort by North Korea to hijack funds from the crypto 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.' More than $500 million was siphoned across the Drift and Kelp exploits in just over two weeks. The Kelp exploit did not involve breaking encryption but rather manipulating the data fed into the system, forcing it to rely on compromised inputs and approve transactions that never occurred. This highlights a security failure where the system checked the sender's identity but not the truthfulness of the message. Experts consider this less about a new hacking technique and more about exploiting the system's setup. The attack wasn't about breaking cryptography; it was about exploiting the system's configuration. A key issue was the reliance on a single verifier to approve cross-chain messages, which, although faster and simpler to set up, removes a critical safety layer. In response, LayerZero has recommended using multiple independent verifiers, similar to requiring multiple signatures on a bank transfer. However, some argue that LayerZero's default setup was to have a single verifier, and if a configuration is identified as unsafe, it should not be shipped as an option. The impact has not been limited to Kelp, as its assets are used across multiple platforms, and problems can spread. This situation exposes a gap between the marketing of decentralization and its actual implementation. A single verifier is not decentralized; it's a centralized decentralized verifier. 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. This means even seemingly decentralized systems can have weak points, especially in less visible layers. The recent targeting by Lazarus, a group tied to North Korea, of cross-chain and restaking infrastructure, which are critical but complex and hold large amounts of value, may explain this shift. These layers are harder to monitor and easier to misconfigure, making them attractive targets. 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 weakness; it showed how exposed the ecosystem remains to familiar ones, especially when security is treated as a recommendation rather than a requirement.