North Korea's Cryptocurrency Theft Tactics Are Evolving, with DeFi Being a Prime Target

Barely three weeks after hackers linked to North Korea used social engineering to breach the cryptocurrency 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 now exploiting fundamental assumptions built into decentralized systems, rather than just seeking out bugs or stolen credentials. The cumulative effect of these incidents suggests a more organized effort by North Korea to siphon funds from the crypto sector, rather than a series of isolated breaches. 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 approve transactions that did not actually occur. As Urbelis noted, 'The security failure is simple: a signed lie is still a lie. Signatures guarantee authorship; they do not guarantee truth.' In essence, the system verified the sender of the message but not the message's accuracy itself. This exploit highlights the vulnerability of systems that rely on a single verifier for cross-chain messages, a configuration choice made for simplicity and speed but at the cost of a critical safety layer. In response, LayerZero has recommended the use of multiple independent verifiers to approve transactions, akin to requiring multiple signatures on a bank transfer. However, some have argued that LayerZero's default setup was to use a single verifier, raising questions about the responsibility of developers to ensure secure configurations. 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 has not been contained, as the assets involved are used across multiple platforms, leading to a wider stress event. Lending platforms like Aave, which accepted the impacted assets as collateral, are now facing losses. This incident also reveals a discrepancy between the marketing of decentralization and its actual implementation. 'A single verifier is not decentralized,' Schwed stated. '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.' 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 underscores this shift. These layers, critical for moving assets between systems or reusing them, are complex and often overlooked, yet they hold significant value, making them attractive targets. As the crypto sector continues to evolve, the biggest risk may not be unknown vulnerabilities but rather known ones that are not fully addressed. The Kelp exploit did not introduce a new kind of weakness; instead, it highlighted how exposed the ecosystem remains to familiar vulnerabilities, 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 more expensive to ignore.