The cryptocurrency world was shaken in mid-December 2023 when a sophisticated supply chain attack targeted the Ledger Connect Kit, a widely used JavaScript library that connects decentralized applications to Ledger hardware wallets. The breach resulted in the theft of approximately $600,000 in digital assets and exposed a critical vulnerability in how Web3 projects manage their software dependencies.
The Exploit Mechanics
The attack unfolded on the evening of December 14, 2023, when an attacker managed to push malicious versions of the @ledgerhq/connect-kit NPM package—specifically versions 1.1.5, 1.1.6, and 1.1.7. The attacker gained access by compromising a former Ledger employee through a phishing campaign, which provided the credentials necessary to publish the tainted packages to the NPM registry.
Once installed, the malicious code replaced the normal window logic with a Drainer class that triggered a fake popup interface mimicking the legitimate Ledger connection dialog. This rogue code handled the transfer logic for various crypto assets, silently redirecting user funds to the attacker-controlled wallet address. The malicious JavaScript was distributed via CDN, meaning any dApp that pulled the latest version of the library automatically served the compromised code to its users.
Security researchers at SlowMist identified that the code in version 1.1.5 referenced “Inferno,” believed to be connected to the Inferno Drainer phishing gang notorious for multi-chain scams. The subsequent versions contained additional obfuscated malicious payloads designed to evade detection.
Affected Systems
The reach of this attack was extraordinary because the Ledger Connect Kit is integrated into hundreds of decentralized applications. Among the platforms directly affected were Zapper, the DeFi asset management protocol whose front-end was first reported as hijacked; Sushi, the decentralized exchange whose CTO Matthew Lilley issued an urgent warning to users; Revoke.cash, the popular token approval management tool; and Kyber Network, the cross-chain DEX aggregator that disabled its front-end as a precaution.
Even MetaMask issued advisories, recommending users enable the Blockaid security feature before executing any transactions. The total losses were estimated at approximately $600,000, though the potential damage could have been far greater had the malicious packages not been detected and replaced within hours.
The Mitigation Strategy
Ledger responded swiftly once the breach was identified. The company pushed a genuine version of the Connect Kit to replace the malicious file on NPM and CDN. Ledger emphasized that the Ledger hardware devices themselves and the Ledger Live application were never compromised—the attack was purely a software supply chain issue affecting the JavaScript connector library.
The broader industry response included multiple dApps temporarily shutting down their front-ends, security teams auditing their dependency trees, and increased scrutiny of NPM package ownership and publishing credentials. This incident highlighted the cascading risks inherent in shared software dependencies across the Web3 ecosystem.
Lessons Learned
The Ledger Connect Kit attack demonstrated that even hardware wallet users are not immune to software-level compromises. Several critical lessons emerged from this incident:
Supply chain attacks are a systemic risk. A single compromised package can affect hundreds of downstream applications simultaneously. Web3 projects must implement rigorous dependency auditing and consider pinning specific package versions rather than always pulling the latest release.
Employee credential security matters. The initial compromise came through phishing a former employee whose access credentials were still active. Companies must have robust offboarding procedures that immediately revoke access to critical publishing infrastructure.
Speed of response is critical. The relatively contained losses—$600,000 rather than tens of millions—were largely due to rapid detection and response by the community and Ledger’s security team.
User Action Required
If you interacted with any dApps between December 14-15, 2023, consider the following steps: revoke all outstanding token approvals through a trusted interface, verify that your Ledger firmware is up to date through Ledger Live, enable transaction simulation features in wallets like MetaMask, and always verify the URL of any dApp before connecting your wallet. Bitcoin traded at approximately $42,270 at the time of this incident, and the broader crypto market capitalization stood near $1.64 trillion, underscoring the scale of assets potentially exposed to such supply chain vulnerabilities.
Disclaimer: This article is for informational purposes only and does not constitute financial or security advice. Always conduct your own research and consult with security professionals regarding asset protection.
the crazy part is it only took ONE compromised former employee to cascade across hundreds of dApps. $600K is honestly getting off easy for this kind of attack vector
one ex-employee with stale credentials and no 2FA rotation. this is a people problem dressed up as a tech problem
Kira V. its worse than a people problem. the whole npm ecosystem has no forced offboarding. every abandoned package is a ticking bomb
exactly this. SAML rotation and offboarding should be automated at every org. the fact that a former employee still had publish access to an npm package with millions of downloads is a governance failure, not a code vulnerability
$600K is the direct drain but the reputational damage to ledger was way worse. every dApp using connect-kit had to emergency patch. the blast radius of one package is insane
nonce_zero the blast radius was insane. every dApp importing connect-kit-frontend got the malicious version. one package, hundreds of apps compromised
one ex-employee phished, npm publish access still active, no 2FA rotation. 600K drained because basic offboarding doesnt exist in web3 infra
versions 1.1.5 through 1.1.7 were live for how long before anyone noticed? supply chain attacks move faster than audit cycles
^ basically a few hours. the drainer class replaced the popup window logic silently. most users had zero clue until funds were already gone
the real question is how many other npm packages have the same access control gap. ledger was just the one that got caught
the drainer class replaced the window object silently. users saw a popup that looked exactly like Ledger and approved. social engineering at the code level
a former employee got phished and nobody thought to revoke their npm publish access. $600K gone because of basic opsec failure
a former employee falling for phishing and that being enough to push malicious NPM packages. the access revocation process at Ledger was basically nonexistent
a phishing email took down a multi billion dollar hardware wallet company. not zero day, not nation state, just regular old phishing. opsec is always the weakest link
600k stolen because NPM had no multi factor on package publishing in 2023. the entire JS ecosystem is held together with tape and goodwill
every dapp importing @ledgerhq/connect-kit got the malicious version. the blast radius was insane for a single dependency
the drainer class replacing the window logic was elegant tbh. fake popup looked identical to the real Ledger UI. users never had a chance
one phished former employee and $600K gone. npm still has no mandatory 2FA for package publishing in 2026. the entire JS ecosystem runs on trust
Lina F. npm 2FA adoption for maintainers is still under 40%. every major package is one phishing email away from a supply chain attack
a phished former employee pushing 3 malicious NPM versions in one evening. no 2FA on publishing, no rollback capability, no staged rollout. every Web3 library should be treating their npm access like nuclear codes by now
the Drainer class was surprisingly sophisticated. fake popup that looked pixel-perfect to the real Ledger UI. $600K stolen is actually low considering how many dApps loaded the compromised package
^ the scary part is the attacker only needed one compromised credential. no multisig on npm publishing, no canary release. the entire JS supply chain is held together with tape