npm: Coordinated Burst of 40 Malicious 'allied' and 'alleged' Packages in 2 Minutes
On August 31, 2026, 40 malicious npm packages, predominantly featuring 'allied' and 'alleged' prefixes in their names, were disclosed within an exceptionally tight two-minute window, signaling a coordinated supply chain attack.
Key findings
- 40 malicious npm packages disclosed within a 2-minute window on August 31, 2026.
- Packages share 'allied' and 'alleged' prefixes, often with animal names and suffixes like
_z3n. - All packages are rated 'Critical' severity, indicating severe system compromise upon installation.
- Behavioral analysis confirms execution of malicious commands by at least one package.
- Campaign suggests automated generation and deployment of malicious dependencies.
- Many packages were first published months to over two years prior to disclosure.
On August 31, 2026, 40 malicious npm packages were disclosed within a tight two-minute window, from 23:13 UTC to 23:15 UTC. This rapid, coordinated burst primarily featured packages adopting 'allied' and 'alleged' prefixes, often combined with animal names and specific suffixes, indicating a deliberate campaign targeting the npm ecosystem.
Campaign Signature
The campaign is characterized by a distinct naming convention, predominantly using prefixes such as allied_ and alleged_, often followed by animal names. Many of these packages also incorporate specific suffixes like _z3n, _0xrequest, -silentdev, -appteadev, or -smiletea. Examples include allied_wombat_z3n, alleged_albatross_z3n, allied_tiger_0xrequest, and allied-harlequin-muskox. The first_published dates for many of these patterned packages range from several months to over two years prior to their disclosure, suggesting a pre-staged infrastructure or a long-running campaign rather than immediate typosquatting.
Malicious Behavior
Analysis of the disclosed packages, such as ally-call-wait-time (version 99.99.99), reveals that they are designed to execute malicious commands upon installation. While specific command details are not fully enumerated for all packages, the consistent 'Critical' severity rating across the board, coupled with the behavioral findings from OpenSSF Package Analysis, indicates a common modus operandi focused on system compromise. The goal of such command execution typically involves exfiltrating sensitive environment variables, installing further malware, or establishing persistent access to the compromised system.
Severity and Impact
The consistent 'Critical' severity assigned to all 40 packages underscores the severe risk posed to any system that installed these malicious versions. Developers are advised to consider any machine that installed these packages as fully compromised. Immediate action, including rotating all credentials and secrets from a separate, clean machine, is strongly recommended to mitigate potential damage.
Detection and Response
Organizations and individual developers should immediately audit their package-lock.json or yarn.lock files for the presence of any packages matching the described naming patterns. A representative list of affected packages includes:
ally-call-wait-timeallied_wombat_z3nalleged_albatross_z3nallied_tiger_0xrequestallied-harlequin-muskoxalleged_pinniped-appteadevallthejs
If any are found, immediate removal and a thorough security audit are paramount. Additionally, checking npm token logs for unauthorized publish events can help identify potential account compromises.
Broader Context
This coordinated disclosure highlights the ongoing challenge of supply chain security in public package registries. The use of distinct naming patterns and rapid deployment within a short timeframe suggests a sophisticated actor or automated tooling. While the immediate threat has been mitigated by the advisories, the incident serves as a reminder for developers to maintain vigilance and implement robust security practices when incorporating third-party dependencies.