North Korea's Cryptocurrency Exploitation 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 significant exploit has been carried out, this time targeting Kelp, a restaking protocol connected to LayerZero's cross-chain infrastructure. This attack suggests an evolution in the tactics employed by North Korea-linked hackers, as they are no longer solely focusing on exploiting bugs or stolen credentials but are now manipulating the fundamental assumptions built into decentralized systems. The combined impact of these two incidents points to a more organized effort by North Korea to hijack 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.' More than $500 million was siphoned off through the Drift and Kelp exploits 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 never actually occurred. 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 key issue with the system's configuration, which relied on a single verifier to approve cross-chain messages, a setup that, 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 in the ecosystem have pushed back against this recommendation, arguing that LayerZero's default setup was to have a single verifier. 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 fallout from the Kelp exploit has not been limited to the platform itself, as its assets are used 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 incident also exposes the 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 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 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 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. As attackers move faster, this gap is becoming both easier to exploit and far more expensive to ignore.