North Korea's Cryptocurrency Hacking Tactics Are Evolving, with DeFi as a Prime Target

Barely three weeks after hackers linked to North Korea employed social engineering tactics to breach the cryptocurrency trading firm Drift, it appears that another significant exploit has been carried out against Kelp, a restaking protocol connected to LayerZero's cross-chain infrastructure. This attack signifies an evolution in the tactics used by North Korea-linked hackers, as they now exploit fundamental assumptions built into decentralized systems, rather than merely seeking vulnerabilities or stolen credentials. The cumulative effect of these incidents suggests a more organized effort by North Korea to siphon 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 isolated incidents, but a cadence. You cannot resolve these issues simply by patching; it's about addressing a procurement schedule.' The combined Drift and Kelp exploits have 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, attackers manipulated the data fed into the system, forcing it to rely on compromised inputs and approve fictitious transactions. 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 message's accuracy. This exploit highlights the issue of configuration choices, with Kelp relying on a single verifier to approve cross-chain messages, which, although faster and simpler to set up, removes a critical safety layer. Following the incident, LayerZero 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 offer it as an option. Security that depends on everyone reading the documentation and getting it right is not realistic.' The fallout from the exploit has not been contained to Kelp, as its assets are utilized 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 attack also reveals a 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 further elaborated, 'Decentralization is not a property a system possesses; it's 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 the Lazarus group can be attributed to this shift, as they begin to focus on cross-chain and restaking infrastructure, the parts of the cryptocurrency sector that move assets between systems or allow them to be reused. These layers are critical but complex, often underlying more visible applications, and they tend to hold large amounts of value, making them attractive targets. If earlier waves of cryptocurrency hacks focused on exchanges or obvious code flaws, recent activity suggests a move toward the industry's underlying infrastructure, the systems that connect everything together but are harder to monitor and easier to misconfigure. 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 vulnerabilities, 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.