North Korea's Expanding Crypto Theft Strategy Targets DeFi

Less than three weeks after North Korea-linked hackers used social engineering to breach crypto trading firm Drift, another major exploit has been attributed to hackers tied to the nation, this time targeting Kelp, a restaking protocol connected to LayerZero's cross-chain infrastructure. This attack suggests an evolution in tactics, as North Korea-linked hackers are now exploiting fundamental assumptions in decentralized systems, not just seeking bugs or stolen credentials. The combined incidents of Drift and Kelp point to a more organized effort by North Korea to hijack crypto sector funds. 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, which did not involve breaking encryption, manipulated data inputs to force the system to approve non-existent transactions. 'The security failure is simple: a signed lie is still a lie,' Urbelis noted. 'Signatures guarantee authorship; they do not guarantee truth.' This highlights a systemic issue rather than a sophisticated new hack, exploiting how the system was set up. David Schwed, COO of blockchain security firm SVRN, emphasized, 'This attack wasn’t about breaking cryptography; it was 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, removes a critical safety layer. LayerZero has since recommended using multiple independent verifiers, akin to requiring multiple signatures on a bank transfer. However, some argue that LayerZero’s default setup was to have a single verifier, and the onus should not be on users to configure security properly. 'If you’ve identified a configuration as unsafe, don’t ship it as an option,' Schwed advised. The impact has not been contained, as assets used across multiple platforms can spread problems. 'These assets are a chain of IOUs,' Schwed said. 'And the chain is only as strong as the controls on each link.' When one link breaks, others are affected, turning a single exploit into a wider stress event, such as lending platforms like Aave dealing with losses after accepting impacted assets as collateral. The attack also reveals a gap between the marketing of decentralization and its actual implementation. 'A single verifier is not decentralized,' Schwed stated. 'It’s a centralized decentralized verifier.' Urbelis broadened this perspective, '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, even seemingly decentralized systems can have weak points, especially in less visible layers. The recent targeting by Lazarus, a group linked to North Korea, of cross-chain and restaking infrastructure underscores this. These layers, critical for moving assets between systems, are complex, often under visible applications, and hold large amounts of value, making them attractive targets. The shift in targeting suggests a move towards what could be called the industry’s plumbing, the systems that connect everything together but are harder to monitor and easier to misconfigure. As Lazarus adapts, 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 but showed how exposed the ecosystem remains to familiar ones, especially when security is treated as a recommendation rather than a requirement. As attackers move faster, this gap is becoming both easier to exploit and far more expensive to ignore.