npm: 31 Malicious 'Tailwind' and 'AnimateCSS' Themed Packages Disclosed in Coordinated 9-Minute Drop
On October 20, 2026, 31 malicious npm packages, many impersonating popular animation and styling libraries like Tailwind CSS and Animate.css, were disclosed within a tight 9-minute window.

Key findings
- 31 malicious npm packages disclosed within a 9-minute window on October 20, 2026.
- Many packages impersonated Tailwind CSS and Animate.css related libraries.
- Several packages were fresh typosquats, published just one day before disclosure.
- Behavioral analysis revealed communication with malicious domains.
- All disclosed packages were rated with Critical severity.
On October 20, 2026, the npm registry experienced a significant supply chain security incident with the coordinated disclosure of 31 malicious packages. All advisories were published within an exceptionally tight 9-minute window, from 06:31 UTC to 06:40 UTC, signaling a deliberate and rapid deployment by a single threat actor or group. This burst included packages designed to impersonate popular front-end development libraries, notably those related to Tailwind CSS and Animate.css, alongside several seemingly ad-hoc typosquats targeting other projects. The consistent 'Critical' severity ratings across all disclosures underscore the severe and immediate threat these packages posed to any development environment or application that might have incorporated them.
The naming strategy employed in this campaign exhibited a clear dual approach. A substantial portion of the malicious packages leveraged names that either directly referenced or closely mimicked established and widely-used front-end development tools, particularly those focused on animation and styling frameworks. Examples of these thematic impersonations include tailwind-keyframes, tailwindcss-animatemotion, animatecss-tailwind-helper, animate-twcss-pack, tailwind-fabric, animatecss-tailwind-binary, tailwindcss-keyframe-kit, and tailwind-animate-catalog. Many of these packages, such as tailwind-keyframes (first published on September 28, 2026) and tailwindcss-visual-kit (first published on October 9, 2026), had been present on the registry for several weeks, quietly accumulating a small number of downloads (e.g., tailwind-keyframes with 10 weekly downloads, tailwindcss-visual-kit with 23 weekly downloads) before their malicious nature was discovered. This suggests a patient approach to establish presence. Concurrently, the burst also contained packages that appeared to be fresh, ad-hoc typosquats or direct impersonations of specific, potentially internal, project names. Notable examples include sc-wizard, fanarena-common, ccl-global-shopping, and sc-announcer, all of which were first published on October 19, 2026 – just one day prior to their disclosure. Another outlier, @platform-services/hrm-mfe-core, also communicated with a malicious domain, highlighting the varied targets within this single coordinated operation.
Analysis from OpenSSF Package Analysis consistently identified a critical behavioral pattern across many of the disclosed packages: communication with domains associated with malicious activity. This finding, explicitly noted for packages such as sc-wizard, fanarena-common, sc-announcer, ccl-global-shopping, and @platform-services/hrm-mfe-core, is a strong indicator of an attempt to establish command-and-control (C2) channels. Such C2 communication typically serves multiple nefarious purposes, including the exfiltration of sensitive data (such as environment variables, API keys, or configuration files), the download and execution of additional malware, or the remote control of compromised systems. The uniformity in this reported behavior across a seemingly disparate set of package names strongly suggests a single, sophisticated threat actor employing a consistent and dangerous attack methodology, aiming to gain persistent access and control over infected development environments or production systems.
The consistent 'Critical' severity ratings assigned to all 31 advisories underscore the profound and immediate risk these packages posed to any system that installed them. In the context of software supply chain attacks, a 'Critical' severity typically implies that the affected machine should be considered fully compromised. This means that the attacker likely gained unauthorized access with significant privileges, potentially allowing them to read, modify, or delete files, execute arbitrary code, or access sensitive network resources. For developers, this translates to a severe breach of trust and security, necessitating immediate and comprehensive remediation. The potential impact ranges from intellectual property theft and credential compromise to the injection of further malicious code into downstream projects, creating a ripple effect across the supply chain.
Given the critical nature of this coordinated attack, developers and organizations are strongly advised to immediately audit their dependency trees for the presence of any of these malicious packages. This can be done by inspecting package-lock.json or yarn.lock files. If any of the affected packages are identified, immediate and decisive action is paramount. Remediation steps should include:
- Isolation: Isolate any compromised systems or development environments from the network.
- Removal: Thoroughly remove the malicious dependency and any associated artifacts.
- Credential Rotation: Rotate all potentially exposed credentials, including API keys, tokens, and passwords, particularly those used in CI/CD pipelines or for publishing to npm. This rotation should ideally be performed from a separate, untainted machine.
- Log Review: Meticulously review npm token logs, system logs, and network traffic logs for any unauthorized activity that might indicate a broader account compromise or data exfiltration.
A representative list of affected packages to specifically search for includes: tailwind-keyframes (affected version = 2.0.6) tailwindcss-animatemotion (affected version = 1.0.7) animatecss-tailwind-helper (affected version = 2.0.6) sc-wizard (affected version = 99.9.1) @platform-services/hrm-mfe-core (affected version 99.9.1) fanarena-common (affected version = 99.9.1) ccl-global-shopping (affected version = 99.9.1) The presence of any of these, or the other 24 packages disclosed in this burst, warrants a full security incident response.
This coordinated burst, encompassing both targeted thematic impersonations and opportunistic typosquats deployed within an extremely tight timeframe, serves as a stark reminder of the persistent and evolving threats within the open-source software supply chain. The ability of threat actors to deploy a significant number of malicious packages so rapidly highlights the sophisticated nature of these attacks and the continuous challenge in maintaining the integrity of widely-used package ecosystems. It underscores the critical need for continuous vigilance, robust automated scanning, and rapid response mechanisms within package registries, as well as proactive security practices within development workflows, to mitigate the impact of such pervasive supply chain compromises.