Ledger Connect Kit serves a wallet drainer to crypto apps
ATG-class event14 December 2023
An attacker who phished a former employee’s npm account published three versions of a library that many crypto apps load in the browser. For about five hours those apps showed users a drainer that asked them to sign away their funds.
- Position
- The publishing account of a front-end library loaded by third-party apps
- Reach
- Decentralized apps that loaded Connect Kit; about $600,000 in affected assets (Ledger)
- Category
- Open-Source Maintainer Infiltration
- Effect
- Deceive
What happened
Ledger Connect Kit is a JavaScript library that decentralized apps load so users can connect a Ledger wallet. On 14 December 2023 an attacker who had phished a former Ledger employee used a session token to enter that person's npm account, bypassing two-factor authentication, and published three malicious versions within two hours. Apps that loaded the library served a drainer kit that asked users to sign transactions sending their funds to the attacker. Ledger learned of it at about 12:45 UTC and shipped a clean version within about forty minutes, but cached copies kept the malicious file reachable for a while longer. Ledger put active draining at under two hours and losses at about $600,000, and promised to reimburse victims.
The ATG nexus
None of the affected apps was breached. Each loaded the library from a source it had every reason to trust, and the library rendered a prompt inside the app's own page. The user saw a request from the app they meant to use and signed it. The hardware wallet did its job, faithfully signing what the user approved, and that was the problem: the deception happened one layer above it, on the screen that framed the request. Caching then stretched the exposure past the moment the fix shipped, a point the research makes about Remote Cache Control.
Limits of the comparison
Ledger's hardware and its users' seed phrases were not compromised. Users who read the transaction details on their device closely could have caught the mismatch.
On this site
- Whitepaper, Chapter 9: Open Source and the Path to the Client Runtime
- Introduction: Swapping What You See
- Concept: Supply Chain Injection
- Concept: Content Swapping
- Concept: Remote Cache Control