npm: 18 Malicious Packages Disclosed in 1-Minute Window
On August 30, 2026, 18 malicious npm packages were disclosed within a single minute, indicating a rapid, coordinated takedown of newly published threats.
Key findings
- 18 malicious npm packages were disclosed on August 30, 2026.
- All advisories were published within a single minute, between 16:33 UTC and 16:35 UTC.
- Many packages were newly published, some just hours before their disclosure.
- Several packages exhibited typosquatting patterns (e.g.,
cloudfcrxz,cloufcrxz) or thematic naming (e.g.,codexsuffix). - All GitHub Security Advisories (GHSAs) for these packages were rated Critical severity.
On August 30, 2026, 18 malicious packages were disclosed on npm within a single minute, between 16:33 UTC and 16:35 UTC. All of these packages were newly published, many just hours before their disclosure, suggesting a rapid response to a coordinated malicious upload event.
While no single, overarching naming pattern like a shared scope or prefix was immediately evident across all packages, several exhibit characteristics of typosquatting or thematic grouping. For instance, cloudfcrxz and cloufcrxz are clear typosquats of each other or a common target. Other packages like h2-codex, h3-codex, and brat-codex share a codex suffix, suggesting a thematic link. The scoped package @fidzzhost/baileys and others such as real-browser-plus and originaldevelopmentstelemetry were also part of this burst. The extremely tight disclosure window, with all advisories landing within 60 seconds, serves as the primary evidence of a single, coordinated malicious campaign or a rapid, synchronized takedown by security teams.
Specific behavioral findings from OpenSSF Package Analysis were not provided for these advisories. However, the critical severity assigned to many of these packages by GitHub Security Advisories (GHSAs) typically indicates highly dangerous behaviors. Such behaviors commonly include arbitrary code execution, credential exfiltration, or system compromise, which can lead to a complete compromise of the affected development environment or build system.
The majority of the disclosed packages were assigned a Critical severity rating. This implies that any system that installed these malicious packages should be considered fully compromised. Developers are strongly advised to treat such an incident with the highest urgency, rotating all sensitive credentials and API keys from a separate, clean machine, and thoroughly auditing their development environments for any lingering malicious artifacts.
Developers should immediately audit their package-lock.json or yarn.lock files for the presence of any of the following package names:
@fidzzhost/baileyscloudfcrxzh3-codexbrat-codexcloufcrxzh2-codexh3clientreal-browser-plusoriginaldevelopmentstelemetry
If found, these packages must be removed, and a full security review of the affected system is recommended. Additionally, organizations should check their npm token logs for any unauthorized publish activity related to their accounts, which could indicate a compromised maintainer account.
This rapid disclosure of multiple newly published malicious packages within a minute highlights the ongoing challenge of defending software supply chains. While the specific actor or motivation behind this particular burst is not detailed, such tightly coordinated drops often represent attempts to quickly distribute malware before detection mechanisms can fully react. This incident underscores the critical need for continuous vigilance and automated security tooling within the npm ecosystem to identify and mitigate emerging threats swiftly.