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

Barely three weeks after North Korea-linked hackers utilized social engineering to breach the crypto trading firm Drift, it appears that hackers associated with the nation have executed another significant exploit, this time targeting Kelp. The attack on Kelp, a restaking protocol integrated into LayerZero's cross-chain infrastructure, signifies an evolution in the tactics employed by North Korea-linked hackers. Rather than solely seeking out vulnerabilities or stolen credentials, they are now exploiting fundamental assumptions underlying decentralized systems. The combined incidents of Drift and Kelp suggest a more organized effort, as North Korea intensifies its endeavors to divert 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 isolated incidents, but rather a cadence. You cannot resolve these issues merely by patching them, as they are rooted in 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, the attackers manipulated the data fed into the system, forcing it to rely on compromised inputs and thereby approving transactions that never actually occurred. As Urbelis noted, 'A signed lie is still a lie. Signatures guarantee authorship, not truth.' In essence, the system verified the sender of the message but not the accuracy of the message itself. For security experts, this exploit highlights the manipulation of the system's setup rather than the introduction of a novel hacking technique. David Schwed, COO of blockchain security firm SVRN, stated, 'This attack was not about breaking cryptography, but about exploiting the system's configuration.' A key issue was the configuration choice of relying on a single verifier to approve cross-chain messages, which, although faster and simpler to set up, removes a critical safety layer. In the aftermath, 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 disputed this framing, arguing that LayerZero's default setup was to have a single verifier. Schwed emphasized, 'If a configuration is identified as unsafe, it should not be shipped as an option. Security that depends on everyone reading the documentation and getting it right is not realistic.' The fallout from the Kelp exploit has not been contained, as its assets are utilized across multiple platforms, leading to a wider stress event. Schwed explained, 'These assets are a chain of IOUs, and the chain is only as strong as the controls on each link.' When one link breaks, others are affected, resulting in lending platforms like Aave, which accepted the impacted assets as collateral, now dealing with losses. The attack also exposes a disparity between the marketing of decentralization and its actual implementation. As Schwed noted, 'A single verifier is not decentralized; it's a centralized decentralized verifier.' Urbelis broadened this perspective, 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 like data providers or infrastructure, which are increasingly the focus of attackers. This shift may explain the recent targeting by the Lazarus group, which has begun focusing on cross-chain and restaking infrastructure, the parts of crypto that move assets between systems or allow them to be reused. These layers are critical but complex, often sitting underneath more visible applications, and tend to 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; it demonstrated how exposed the ecosystem remains to familiar ones, especially when security is treated as a recommendation rather than a requirement. And as attackers move faster, this gap is becoming both easier to exploit and far more expensive to ignore.