Latest / Decrypted: The UK Cyber Briefing / The npm maintainer account North Korea phished, and the four packages it unlocked
Transcript
- 0:03This is Decrypted. Friday, the thirty-first of July.
- 0:07The npm maintainer account North Korea phished, and the four packages it unlocked.
- 0:15Amazon's threat intelligence team said this week that four separate compromises of open source JavaScript pa
- 0:23ckages, running from March 2025 to March 2026, were the work of the same North Korea linked group.
- 0:31And they used the same method every time.
- 0:34Not a software flaw. A phished maintainer.
- 0:38The packages named matter less than what this says about how modern software is put together.
- 0:44Debug, chalk and axios aren't things anyone chooses to install.
- 0:50They turn up automatically, as dependencies of dependencies, buried several layers deep in most things built
- 0:57with Node.js over the past decade.
- 1:00Next. What actually happened.
- 1:03Amazon assesses, with medium confidence, that the group behind it is the North Korea linked one it tracks as
- 1:10Sapphire Sleet. You may also know it as Stardust Chollima, BlueNoroff, CageyChameleon or Alluring Pisces.
- 1:19It started small. The typo-crypto package was trojanised in March 2025, apparently as a trial run.
- 1:27Then it escalated. In September 2025 came debug and chalk, two of the most widely used JavaScript utility lib
- 1:37raries. Amazon says that event reached roughly one in ten cloud environments within a two hour window, citing
- 1:45research from Wiz.
- 1:54ds.
- 2:00Then they published a malicious update under that maintainer's own, legitimate credentials.
- 2:06The motive fits a familiar pattern.
- 2:09North Korea has leaned on cyber theft to fund itself around sanctions.
- 2:14It stole more than two billion dollars in cryptocurrency in 2025 alone.
- 2:19And finally. The Secure by Design lesson.
- 2:22Think of it as a single master key, handed to a building caretaker on the strength of a friendly email.
- 2:29If someone tricks the caretaker into giving it up, every flat in the block is exposed at once.
- 2:35And the lock can't tell the caretaker's key from a stranger's.
- 2:38A maintainer's publish credentials work the same way across the npm ecosystem.
- 2:44Whoever holds them can push code that quietly becomes part of every application depending on that package.
- 2:51Usually with no human review at the point of consumption.
- 2:54The fix isn't "stop using open source".
- 2:58That's not realistic. The fix is engineering that assumes a maintainer account will eventually be compromised
- 3:05, and stops that becoming an instant, wide cascade.
- 3:08That means signed publishes with verifiable provenance, which npm now supports.
- 3:14It means lockfiles pinned to content hashes, rather than loose version ranges.
- 3:20And it means a deliberate delay before newly published versions are pulled automatically into a build pipelin
- 3:26e, so an anomaly has time to surface before it reaches production.
- 3:31None of this is exotic. It's the same lesson the industry drew from the xz-utils backdoor, uncovered in 2024
- 3:39. And on this week's evidence, it's one the industry still hasn't fully absorbed.
- 3:44Any UK organisation running Node.
- 3:47js, which is most of them, inherits this exposure.
- 3:51Whether or not it has ever heard of Sapphire Sleet.
- 3:54That was Decrypted. The written version and every source are linked in the show notes.
- 3:59Thanks for listening.