North Korea's Cryptocurrency Theft Tactics Are Evolving, with DeFi Being Frequently Targeted

Barely three weeks after hackers linked to North Korea used social engineering to breach the cryptocurrency trading firm Drift, it appears that hackers from the same nation have successfully executed another significant exploit, this time targeting Kelp, a restaking protocol integrated into LayerZero's cross-chain infrastructure. This attack signifies an evolution in the tactics employed by North Korea-linked hackers, who are now not only seeking vulnerabilities or stolen credentials but are also exploiting fundamental assumptions underlying decentralized systems. The cumulative effect of these incidents suggests a more organized effort than isolated hacks, as North Korea continues to escalate its attempts to divert funds from the cryptocurrency 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 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 how the system was set up to prioritize speed and simplicity over security, relying on a single verifier to approve cross-chain messages. The aftermath has seen recommendations for using multiple independent verifiers to approve transactions, akin to requiring multiple signatures on a bank transfer. However, some have pushed back against this, arguing 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 impact has not been limited to Kelp, as its assets are utilized across multiple platforms, leading to a wider stress event affecting lending platforms like Aave that accepted the impacted assets as collateral. This incident also exposes the disparity 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 further elaborated, '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.' The attack on Kelp and similar infrastructures suggests a shift in focus towards the less visible layers of the crypto ecosystem, such as data providers or infrastructure, where weak points can exist even in systems that appear decentralized. This shift may explain why groups like Lazarus are targeting cross-chain and restaking infrastructure, which are critical for moving assets between systems or allowing them to be reused. These layers are not only complex and harder to monitor but also tend to hold significant 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 reveal a new kind of weakness; instead, it demonstrated how exposed the ecosystem remains to familiar vulnerabilities, especially when security is treated as a recommendation rather than a requirement.