North Korea's Crypto Theft Tactics Are Evolving, with DeFi Being a Prime Target
Barely three weeks after hackers linked to North Korea employed social engineering to breach crypto 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 advancement in the tactics used by North Korea-linked hackers, who are now exploiting fundamental assumptions within decentralized systems, rather than merely seeking out bugs or stolen credentials. The combined impact of these incidents suggests a more organized effort by North Korea to siphon 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.' More than $500 million was siphoned across the Drift and Kelp exploits in just over two weeks. The Kelp breach was facilitated by manipulating the data feeding into the system, forcing it to rely on compromised inputs and thereby approving transactions that never actually occurred. 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 configuration issue where Kelp relied on a single verifier to approve cross-chain messages, a 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 against this recommendation, stating that LayerZero's default setup was to use 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 repercussions of the exploit have extended beyond Kelp, affecting lending platforms like Aave that accepted the impacted assets as collateral, thereby turning a single exploit into a broader stress event. This incident also exposes 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.' This realization underscores that even seemingly decentralized systems can have vulnerabilities, 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 attributed to North Korea, of cross-chain and restaking infrastructure, underscores this shift. These layers, critical to the movement of assets between systems and the reuse of assets, are complex, often less visible, and hold significant value, making them attractive targets. As Lazarus adapts, the most significant risk may not be unknown vulnerabilities but known ones that are not fully addressed. The Kelp exploit did not reveal a new kind of weakness but demonstrated how exposed the ecosystem remains to familiar vulnerabilities, especially when security is treated as a recommendation rather than a requirement. As attackers accelerate their efforts, this gap is becoming both easier to exploit and more costly to ignore.