Malware in tailwindcss-animates-css
Malware discovered in the npm package tailwindcss-animates-css. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- tailwindcss-animates-css
A malware-containing version of the npm package tailwindcss-animates-css has been identified and published to the npm registry. The package is flagged as critical severity by GitHub Security Advisory GHSA-xwr3-cg53-gqv5.\n\nAny computer with this package installed or running should be considered fully compromised. The malware may grant outside entities full control of affected systems.\n\nImmediate action is required to mitigate the compromise, including removal of the package and rotation of all secrets and keys from a separate, uncompromised system. However, complete removal of all malicious software cannot be guaranteed by package removal alone, given the potential for full system compromise.\n
Indicators of compromise
- Packages
- tailwindcss-animates-css
Remediation
- Immediately remove the tailwindcss-animates-css package from all affected systems
- Rotate all secrets, API keys, credentials, and tokens from a separate, uncompromised computer
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and network activity for signs of unauthorized access or data exfiltration
- Consider full system reimaging if complete compromise is suspected
- Monitor for any suspicious activity on accounts or systems that may have been affected
Sources
- GitHub Advisory GHSA-xwr3-cg53-gqv5 · GitHub Advisory Database
Cite this entry
"Malware in tailwindcss-animates-css." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 17, 2026; last updated June 20, 2026. https://supplychainattack.org/incident/malware-in-tailwindcss-animates-css-1n6do9
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit