npm: 40 Malicious 'baileys'-Themed Packages Dropped in Under a Minute
Key findings • 40 malicious npm packages were disclosed in under one minute on November 10, 2026. • Many packages shared a 'baileys' or similar naming convention, indicating a coordinated cam…
Key findings
- 40 malicious npm packages were disclosed in under one minute on November 10, 2026.
- Many packages shared a 'baileys' or similar naming convention, indicating a coordinated campaign.
- All disclosed packages were rated 'Critical' severity, implying severe compromise upon installation.
- Users who installed these packages should consider their systems compromised and rotate all credentials.
- The rapid disclosure demonstrates active monitoring and response to supply chain threats.
On November 10, 2026, a significant coordinated attack unfolded on the npm registry, with 40 malicious packages disclosed within a single minute. This rapid takedown points to a highly organized effort by security teams to remove a burst of threats. The packages, many of which incorporate variations of the term "baileys" in their names, were flagged and removed from the registry on this date, preventing further potential compromise.
While no single clear typosquat target was identified, the prevalence of "baileys" and similar terms across many package names suggests a thematic campaign. This naming convention could be an attempt to impersonate a legitimate project or simply a shared identifier used by the threat actor to group their malicious uploads. Examples of these packages include zexxo-baileys, zenvy-baileys, yuuki-baileys, shadowmd-baileys, and yagami-baileys. The coordinated nature of their release, all within seconds of each other, strongly indicates a single actor or group behind this operation.
Although specific behavioral findings for each package were not detailed, the advisories consistently assigned a 'Critical' severity rating. This typically implies that the packages were designed to execute arbitrary code, exfiltrate sensitive data, or establish persistent access to compromised systems. Malicious packages often employ techniques such as post-install scripts to run arbitrary commands, communicate with attacker-controlled domains, or modify system files. Given the critical severity, any system that installed these packages should be considered fully compromised.
The 'Critical' severity designation means that any computer that installed one of these malicious packages should be treated as compromised. Users are strongly advised to take immediate action, including rotating all credentials, API keys, and sensitive tokens from a separate, secure machine. The compromise could extend to any data accessible by the user account that ran the installation, potentially including source code, configuration files, and cloud service credentials.
Developers should 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 a thorough security audit of the affected environment should be conducted. It is crucial to rotate any credentials that might have been exposed. A partial list of the malicious packages includes:
zakkixd1zexxo-baileyszenvy-baileysyuliawhhzenvyflumpyuuki-baileyszyleyszhenbaileysyazxzyukistageyantobailwizeza-baileysshadowmd-baileysxnxx-bail-provinzzknightyagami-baileys
This burst highlights the ongoing challenge of supply chain security in open-source ecosystems. The speed and coordination of this particular disclosure underscore the persistent efforts of malicious actors to inject harmful code into widely used package managers. Vigilance, robust dependency scanning, and prompt credential rotation remain essential defenses against such sophisticated attacks.