npm: 13 Malicious Packages, Including '@prime0/' Scope, Disclosed in 10-Minute Burst
On September 16, 2026, thirteen malicious npm packages, including a series under the '@prime0/' scope, were disclosed within a tight 10-minute window, indicating a coordinated supply chain attack.
Key findings
- Thirteen malicious npm packages were disclosed on September 16, 2026.
- The disclosures occurred within a tight 10-minute window, indicating coordination.
- Three packages shared the '@prime0/' npm scope, suggesting a targeted campaign.
- Other packages exhibited naming patterns like
discord-*andteto*, hinting at typosquatting or themed attacks. - Malicious packages commonly aim to exfiltrate sensitive data or execute arbitrary commands.
On September 16, 2026, thirteen malicious packages were disclosed on npm within a concentrated 10-minute window, signaling a coordinated attack targeting the software supply chain. This rapid succession of advisories, all published between 06:27 UTC and 06:37 UTC, points to a single, concerted effort by a threat actor or group. A notable aspect of this burst is the presence of packages sharing the @prime0/ scope, which serves as a clear campaign signature within this broader malicious activity.
Further analysis of the disclosed packages reveals several distinct naming patterns, suggesting a multi-pronged approach to compromise. Three packages—@prime0/inimatch, @prime0/pcomatch, and @prime0/alanced-match—all share the @prime0/ npm scope, indicating a direct campaign targeting this specific namespace. Beyond this, other packages exhibit characteristics consistent with typosquatting or themed attacks. For instance, discord-resolvers and discord-players appear to impersonate legitimate Discord-related libraries, with discord-players having been first published just three days prior to its disclosure, and discord-resolvers two days prior, suggesting they were fresh malicious drops. Similarly, tetomood and tetotest share a common teto prefix, while strapi-plugin-pencc-meeb and strapi-plugin-ccsuc-meeb follow a strapi-plugin-*-meeb structure, further illustrating the varied but coordinated nature of this disclosure event. The remaining packages, such as engin1, chai-as-agile, otel-span-adapter, and swnwall, appear to be ad-hoc malicious uploads contributing to the overall burst.
While specific behavioral findings for each package were not detailed, malicious packages in such campaigns typically aim to compromise developer environments. Common tactics include the exfiltration of sensitive data, such as environment variables, API keys, and credentials, to attacker-controlled infrastructure. They may also execute arbitrary commands on the compromised system, potentially leading to further infection, backdoor installation, or lateral movement within a network. Such packages often attempt to establish communication with external domains to serve as command-and-control (C2) servers or data exfiltration points, though specific indicators of compromise (IOCs for this burst were not detailed in the provided information.
The severity of such compromises cannot be overstated. Any system that installed one of these malicious packages should be considered fully compromised. The potential impact ranges from data theft and intellectual property loss to complete system takeover. The stealthy nature of supply chain attacks means that developers might unknowingly integrate malicious code into their projects, propagating the compromise downstream to users of their software. The immediate and critical recommendation is to treat any affected system as compromised and take swift remediation actions.
Developers are strongly advised to audit their package-lock.json or yarn.lock files for the presence of any of the disclosed malicious packages. If found, these packages must be immediately removed, and all associated credentials, including npm tokens, API keys, and other sensitive information, should be rotated from a separate, clean machine. Furthermore, it is crucial to review npm token logs and other security logs for any unauthorized publish events or suspicious activity that might indicate a broader compromise of developer accounts. Examples of packages to look for include: @prime0/inimatch discord-resolvers tetomood strapi-plugin-pencc-meeb engin1 This coordinated burst of malicious package disclosures underscores the persistent and evolving threat landscape in software supply chains. The use of multiple naming conventions within a single, tightly-timed disclosure event highlights attackers' adaptability and their continuous efforts to bypass detection mechanisms. Vigilance, robust security practices, and prompt response to advisories remain paramount for maintaining the integrity of development ecosystems.