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 cryptocurrency trading firm Drift, another significant exploit has been attributed to the nation, this time targeting Kelp, a restaking protocol integrated into LayerZero's cross-chain infrastructure. This attack signifies an evolution in the tactics employed by North Korea-linked hackers, who are now not only exploiting bugs or stolen credentials but also manipulating the fundamental assumptions underlying decentralized systems. The cumulative effect of these incidents suggests a more organized effort by North Korea to siphon 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 isolated incidents; it's a cadence. You cannot resolve these issues simply by patching; it's about addressing the 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 input into the system, forcing it to rely on compromised data and approve transactions that did not actually occur. As Urbelis noted, 'A signed lie is still a lie. Signatures guarantee authorship, not truth.' This exploit highlights a security failure where the system verified the sender of the message but not the accuracy of the message itself. For security experts, this attack is less about a novel hacking technique and more about exploiting the system's configuration. David Schwed, COO of blockchain security firm SVRN, emphasized, 'This attack wasn't about breaking cryptography; it was about exploiting how the system was set up.' A key issue was the use of a single verifier to approve cross-chain messages, a configuration choice that, while faster and simpler to set up, 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, stating that LayerZero's default setup was to use a single verifier. Schwed argued, 'If you've identified a configuration as unsafe, don't offer it as an option. Security that depends on everyone reading the documentation and getting it right is not realistic.' The impact of the exploit has not been limited to Kelp, as its assets are utilized across multiple platforms, leading to a wider stress event. Lending platforms like Aave, which accepted the affected assets as collateral, are now dealing with losses. The incident also exposes a disparity 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 expanded on this, stating, 'Decentralization is not a property a system has; it's a series of choices. And the stack is only as strong as its most centralized layer.' This means that even systems that appear decentralized 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 underscores this shift. These layers are critical but complex and often hold large amounts of value, 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 reveal a new kind of weakness; instead, it demonstrated how exposed the ecosystem remains to familiar vulnerabilities, especially when security is treated as a recommendation rather than a requirement. As attackers move faster, this gap is becoming both easier to exploit and more expensive to ignore.