npm: 19 Malicious Packages Disclosed in Under a Minute
On August 29, 2026, 19 malicious packages were disclosed on npm within a single minute, indicating a highly coordinated attack.
Key findings
- 19 malicious npm packages were disclosed simultaneously at 03:31 UTC on August 29, 2026.
- All packages were assigned a Critical severity rating.
- The burst included both newly published packages and some that had been on the registry for months.
- The extremely tight disclosure window indicates a highly coordinated security response.
- No clear common naming pattern was identified among the malicious packages.
On August 29, 2026, 19 malicious packages were disclosed on npm within a single minute, all at 03:31 UTC. This extremely tight disclosure window points to a highly coordinated takedown effort by security teams, addressing a rapid deployment of malicious code. The packages varied in their publication age, with some like mfacord appearing just three hours before disclosure, while others such as @testrelic/playwright-analytics had been present on the registry for seven months, suggesting a mix of fresh typosquats and potentially compromised older packages.
Despite the lack of a clear common naming pattern, the simultaneous disclosure of all 19 packages confirms they are part of a single, coordinated operation. This burst includes packages with diverse names such as mfacord, secretkey2fa, supersignaturenature, js-tokens-array, and @testrelic/playwright-analytics. The package mfacord was first published only three hours before its disclosure, indicating a very recent malicious upload. In contrast, vs-modules was published two days prior, supersignaturenature three days prior, and @testrelic/playwright-analytics seven months prior, highlighting that the campaign targeted both newly created and potentially older, established package names.
All 19 packages were assigned a Critical severity rating, indicating a high potential for severe impact on affected systems. While specific behavioral findings were not detailed in the advisories, packages with Critical severity typically aim to compromise the integrity, confidentiality, or availability of a developer's environment. This can include actions such as exfiltrating sensitive data, installing backdoors, or executing arbitrary code on the victim's machine.
Given the Critical severity, any system that installed one or more of these packages should be considered fully compromised. The immediate priority for affected users is to isolate compromised systems, rotate all credentials (including API keys, tokens, and passwords) from a separate, secure machine, and thoroughly audit for any unauthorized activity or persistent malicious implants.
Developers should immediately audit their package-lock.json, yarn.lock, or pnpm-lock.yaml files for any of the disclosed package names. If found, these packages must be removed, and a comprehensive security review of the affected project and environment should be conducted. Examples of packages to look for include:
mfacordsecretkey2fasupersignaturenaturejs-tokens-array@testrelic/playwright-analytics
This rapid, coordinated disclosure highlights the ongoing vigilance required in the open-source software supply chain. The ability of security teams to identify and remove a significant number of malicious packages within such a tight timeframe underscores the effectiveness of current detection and response mechanisms, even when faced with varied attack vectors targeting both new and older package identities.