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 crypto trading firm Drift, another significant exploit was carried out against Kelp, a restaking protocol connected to LayerZero's cross-chain infrastructure. This attack suggests an evolution in the tactics used by North Korea-linked hackers, moving beyond exploiting bugs or stolen credentials to manipulating the fundamental assumptions built into decentralized systems. The combined incidents of the Drift and Kelp exploits, which resulted in the theft of over $500 million in just over two weeks, point to a more organized effort by North Korea to intercept 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 incidents; it is a cadence. You cannot patch your way out of a procurement schedule.' The Kelp exploit 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 highlights a critical issue where the system checked the sender's identity but not the message's accuracy. David Schwed, COO of blockchain security firm SVRN, emphasized that the attack was not about breaking cryptography but about exploiting how the system was set up. A key issue was Kelp's reliance on 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 on this recommendation, stating that LayerZero's default setup was to have a single verifier. Schwed argued, '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 limited to Kelp 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. The incident also exposes a gap between the marketing of decentralization and its reality. As Schwed pointed out, '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.' This means that even systems appearing decentralized can have weak points, particularly in less visible layers such as data providers or infrastructure, which are increasingly the focus of attackers. The targeting of cross-chain and restaking infrastructure by groups like Lazarus underscores this shift, as these layers are critical, complex, and hold large amounts of value, making them attractive targets. The move towards targeting the 'plumbing' of the crypto industry, the systems that connect everything together but are harder to monitor and easier to misconfigure, poses significant risks. The Kelp exploit did not reveal a new kind of weakness but 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, the gap between known vulnerabilities and their full addressing is becoming both easier to exploit and more expensive to ignore.