Podcast Reviews npm Package Attacks and a Poisoned VS Code Extension
Summary
The episode discusses malicious npm packages linked to DPRK and TeamPCP, a poisoned Nx Console extension that exposed GitHub repositories, and npm’s staged-publishing feature, including its potential benefits and limitations.
Key points
- The hosts say npm staged publishing adds an interactive human approval step, but it is enabled per package and may not help single-maintainer projects.
- A researcher linked three npm packages to the threat actor behind the March Axios compromise; the packages were reportedly harvesting developer credentials since early April.
- Two npm maintainers were reportedly compromised, enabling TeamPCP to publish more than 600 malicious versions; one maintainer managed over 540 packages.
- The malicious package payloads appeared to contain Mini Shai-Hulud content, but the hosts said they had not been fully analyzed.
- A compromised Nx developer account was used to publish a poisoned Nx Console VS Code extension after a TanStack-related theft of a GitHub CLI OAuth token.
- A GitHub employee installed the extension; GitHub estimated about 3,800 exposed repositories, while the hosts discussed uncertainty about the extension’s availability window.
- The hosts also discussed a CISA repository described as private that was not private, emphasizing secrets visibility, credential rotation, and repository-permission controls.
Article Details
- Event Type
- Multiple supply-chain compromises involving malicious npm packages and a poisoned VS Code extension, including credential theft and compromise of developer and maintainer accounts.
- Impact
- Three npm packages linked to the March Axios compromise reportedly harvested developer credentials from early April. TeamPCP published more than 600 malicious package versions after compromising two npm maintainers; three affected packages had more than 5 million weekly downloads. A malicious Nx Console extension published on May 18 was consumed by a GitHub employee after a developer’s GitHub CLI OAuth token was stolen through the TanStack compromise on May 11. GitHub estimated that approximately 3,800 repositories were exposed; the speakers also mentioned estimates of up to 5,000. The extension was removed from the Visual Studio Marketplace and OpenVSX, though a speaker said it remained obtainable through a CDN or other means beyond the stated removal window.
People
AtulIndividual npm maintainer whose account was reportedly compromised; he maintained 540 packages.Jenn GileCo-host who discussed the npm staged publishing feature and the reported supply-chain incidents.Paul McCartySecurity researcher and speaker who reported discovering the three npm packages linked to the Axios compromise and discussed the TeamPCP and Nx Console incidents.
Threat Actors
DPRKIdentified in the episode as the threat actor behind the March Axios compromise; three npm packages tied to that actor reportedly harvested developer credentials.TeamPCPNamed as responsible for publishing more than 600 malicious npm package versions after maintainer compromises and for the poisoned Nx Console extension incident.
Malware
Vendors
GitHubGitHub Employee Device Compromised via Poisoned VS Code Extension: On May 18th, a malicious version of the Nx Console VS Code extension was published to the Visual Studio Marketplace and OpenVSX. A GitHub employee hadnpmnpm Staged Publishing: npm’s new staged publishing feature adds a human approval checkpoint before a package goes live. We walk through what it actually does, where it would and wouldn’t have helped in recent attacks,NxGitHub Employee Device Compromised via Poisoned VS Code Extension: On May 18th, a malicious version of the Nx Console VS Code extension was published to the Visual Studio Marketplace and OpenVSX. A GitHub employee had
Products
AxiosDPRK Axios-Linked Packages: Paul discovered three npm packages tied to the threat actor behind the March Axios compromise. These packages have been quietly harvesting developer credentials since early April. We discussNx ConsoleEmployee Device Compromised via Poisoned VS Code Extension: On May 18th, a malicious version of the Nx Console VS Code extension was published to the Visual Studio Marketplace and OpenVSX. A GitHub employee had itTanStackhad it installed. The credential theft that made it possible happened seven days earlier, through the TanStack npm compromise. GitHub estimates around 3,800 repositories were exposed. We also discuss the CISAVS CodeGitHub Employee Device Compromised via Poisoned VS Code Extension: On May 18th, a malicious version of the Nx Console VS Code extension was published to the Visual Studio Marketplace and OpenVSX. A GitHub employee had
Tools
GuardDogare just JavaScript — you can run the same analysis on them that you do on npm packages. Tools like GuardDog and MuadDib work on these. The level of inception here just blows my mind: a Microsoft employee using aMuadDibJavaScript — you can run the same analysis on them that you do on npm packages. Tools like GuardDog and MuadDib work on these. The level of inception here just blows my mind: a Microsoft employee using a Microsoft