The npm platform is the target of another supply chain attack, with crims already compromising 187 packages and counting. According to Charlie Eriksen, malware researcher at Aikido, the attacker appears to be the same one who targeted Nx at the end of August – a campaign in which developers' secrets, such as credentials, were posted to public GitHub pages. Socket and Step Security first reported the latest round of attacks on September 15, with 40 packages affected, but Eriksen has since seen 147 additional packages compromised through similar means, including those from security giant CrowdStrike. However, Eriksen said that the attackers "have upped their game," evolving their tradecraft to adopt a self-propagating worm. The way the attack works is that miscreants embed a malicious payload into compromised npm packages, often relied upon by many projects, which then runs on a victim's machine to steal secrets, system information, and credentials. Before moving to the next stage, it runs TruffleHog to scan for secrets. Researchers noted that it specifically looks out for AWS keys, GCP and Azure service credentials, GitHub personal access tokens, cloud metadata endpoints, and npm authentication tokens. In a similar style to the Nx attack, the payload then publishes a new repo via the victim's GitHub account, dropping stolen credentials and tokens, as well as making a double-encoded backup in the victim's GitHub Actions logs in case the command to send the secrets to the attack...
Self-propagating worm fuels latest npm supply chain attack
The Register
·Connor Jones
·Published Sep 16, 2025
·Updated
Affected Software
1 affected component
npm platform
Frequently Asked Questions
1
What is the main topic of this article?
The article discusses a supply chain attack targeting the npm platform involving a self-propagating worm that has compromised 187 packages.
2
What security implications are discussed in the article?
The article highlights the risks posed by supply chain attacks, particularly the impact on the integrity of npm packages and developer trust.
3
What products or software are affected?
The affected software in this incident is the npm platform, specifically the compromised packages within it.
4
Who is identified as the attacker in the npm supply chain attack?
The attacker appears to be the same individual or group responsible for a previous incident involving the Nx software.
5
What should developers do in response to this npm attack?
Developers are advised to review and secure their package dependencies to mitigate risks posed by compromised npm packages.