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 connected to LayerZero's cross-chain infrastructure. This attack signifies an evolution in the tactics employed by North Korean hackers, as they are now exploiting fundamental assumptions built into decentralized systems, rather than merely seeking out vulnerabilities or stolen credentials. The cumulative effect of these incidents points to 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 incidents; it is a cadence. You cannot patch your way out of a procurement schedule.' The exploits on Drift and Kelp 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 fed into the system, forcing it to rely on compromised inputs and approve non-existent transactions. 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 problem not with cryptography, but with how the system was configured. A key issue was the use of a single verifier to approve cross-chain messages, a choice made for speed and simplicity but one that removes a critical safety layer. In response, LayerZero has recommended using multiple independent verifiers, akin to requiring multiple signatures on a bank transfer. However, some argue that LayerZero's default setup was to have a single verifier, raising questions about the balance between security and ease of use. David Schwed, COO of blockchain security firm SVRN, emphasized, '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 extends beyond the platform itself, as its assets are used across multiple DeFi platforms, creating a ripple effect. 'These assets are a chain of IOUs,' Schwed explained. 'And the chain is only as strong as the controls on each link.' When one link breaks, others are affected, leading to a wider stress event. This incident also reveals a disconnect 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 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 the Lazarus group of cross-chain and restaking infrastructure, critical but complex layers that move assets between systems or allow them to be reused, underscores this shift. These layers are not only vital but also hold large amounts of value, making them attractive targets. As the landscape of crypto hacks evolves, 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; it showed how exposed the ecosystem remains to familiar ones, especially when security is treated as a recommendation rather than a requirement. As attackers adapt and move faster, this gap is becoming both easier to exploit and far more expensive to ignore.