npm: 30 Malicious Packages, Including Critical '@fluxionii/baileys' and '@ostyado/baileys', Disclosed in 22-Minute Burst
On October 19, 2026, 30 malicious packages, many impersonating popular animation and styling libraries, were disclosed on the npm registry within a tight 22-minute window, including critical advisories for `@fluxionii/baileys` and `@ostyado/baileys`.

Key findings
- 30 malicious npm packages were disclosed within a 22-minute window on October 19, 2026.
- The campaign utilized thematic naming related to animation and styling frameworks (e.g., Tailwind CSS, Animate.css).
- Specific scoped packages,
@fluxionii/baileysand@ostyado/baileys, were part of the burst. - Several advisories, including for
@fluxionii/baileysand@ostyado/baileys, were rated Critical severity. - Many of the packages were newly published just weeks before their disclosure, indicating fresh malicious drops.
On October 19, 2026, a burst of 30 malicious packages was disclosed on the npm registry, all within a tight 22-minute window. This coordinated disclosure included critical advisories for packages like @fluxionii/baileys and @ostyado/baileys, alongside numerous others adopting names related to animation and styling frameworks such as Tailwind CSS and Animate.css. Many of these packages, such as animatecss-tailwind-helper and tailwindcss-keyframe-kit, were first published just weeks prior to their disclosure, indicating they were likely created specifically for malicious purposes rather than representing a compromise of long-standing projects.
This campaign exhibits a clear thematic signature, with many package names attempting to mimic or associate with popular front-end development tools, particularly those related to animation and styling. Examples include animate-tailwind-kit, animatecss-tailwind-binary, tailwind-animate-kit, tailwindcss-animatemotion, and tailwindcss-visual-kit. Additionally, two distinct sets of packages, @fluxionii/baileys and @ostyado/baileys, suggest a pattern of using specific scopes or prefixes for related malicious drops, further indicating a coordinated effort by the attackers.
While specific behavioral findings for all packages were not detailed in the advisories, the presence of critical severity ratings for packages like @fluxionii/baileys and @ostyado/baileys strongly suggests that any system installing these packages could be severely compromised. Such compromises typically involve unauthorized access, data exfiltration, or the execution of arbitrary code on the affected machine.
The severity of these disclosures is highlighted by the 'Critical' rating assigned to several advisories, including those for @fluxionii/baileys and @ostyado/baileys. This indicates that systems that installed these malicious versions should be considered fully compromised. Such compromises typically necessitate immediate action, including the rotation of all credentials and secrets from a separate, clean machine, as well as thorough system audits to identify and remediate any unauthorized changes or persistent threats.
Developers are advised to audit their package-lock.json or yarn.lock files for the presence of any of the disclosed malicious packages. If found, immediate action is required: remove the package, rotate all sensitive credentials (API keys, tokens, passwords) that may have been exposed, and investigate for further compromise. A partial list of affected packages includes:
@fluxionii/baileys@ostyado/baileysanimate-tailwind-kitanimatecss-tailwind-helpertailwind-animate-kittailwindcss-visual-kit
This coordinated disclosure underscores the persistent threat of supply chain attacks targeting package managers like npm. The use of thematic naming and scoped packages, combined with rapid deployment, indicates a sophisticated approach by attackers to leverage common development patterns for malicious distribution. The swift identification and disclosure of these packages by security researchers highlight the critical importance of continuous monitoring and rapid response mechanisms within the open-source ecosystem.