A new npm supply chain attack is harvesting developer authentication credentials and automatically spreading through packages published from compromised accounts. The attack demonstrates a concerning escalation in threats targeting the Node.js ecosystem.
Security researchers have identified a supply chain attack targeting npm that combines credential theft with self-propagation capabilities. The attack compromises developer accounts and uses those credentials to publish malicious packages, which then infect downstream users and attempt to compromise their accounts as well.
The attack works by injecting code into npm packages that steals authentication tokens when installed. These tokens grant access to npm registries and can be used to publish additional malicious packages or modify existing ones. This creates a chain reaction where each compromised developer potentially exposes their entire network of dependencies.
Unlike previous npm attacks that relied on typosquatting or abandoned packages, this threat leverages legitimate-looking package updates and hijacked developer accounts. This makes detection significantly harder, as the malicious code appears to come from trusted sources.
The attack targets developers across multiple projects simultaneously. Once a token is stolen, attackers can access all packages associated with that developer's account, expanding the blast radius substantially. Organizations using affected packages may unknowingly distribute compromised code to their own users.
The npm security team has been notified and is working to identify and remove malicious packages from the registry. Security researchers recommend developers immediately rotate authentication tokens and review recent package publishing activity on their accounts.
This incident highlights persistent vulnerabilities in open-source supply chains. While npm and similar registries have implemented security measures, determined attackers continue to find ways around them. The self-spreading nature of this attack is particularly concerning, as it can compromise systems faster than security teams can respond.
Developers should audit their dependencies, enable two-factor authentication on npm accounts, and consider using tools that monitor package integrity and flag suspicious updates.
The ShinyHunters extortion group has published sensitive data from nearly 13 million Carhartt customer accounts stolen earlier this month, according to data breach notification service Have I Been Pwned.
A Russian-speaking ransomware gang called Aur0ra exploited SpaceX's Cursor AI coding assistant to breach at least seven companies between mid-April and late May, according to security firm Gambit Security.
Americans are systematically targeting and disabling Flock Safety cameras across the country in a decentralized protest movement. The surveillance devices face everything from vandalism to theft as public opposition intensifies.
The US Justice Department has dismantled online infrastructure used by Chinese state-sponsored hackers targeting NASA, the Federal Reserve, and the Senate. The action represents a coordinated effort to disrupt cyber operations against American government agencies and critical infrastructure.