MalwarePublished 19 Oct 2026Updated 29 Oct 2026

animatecss-tailwind-plugin (npm) · Malicious Code

Affects animatecss-tailwind-pluginSource GCVE Database

Malicious package : remove animatecss-tailwind-plugin and rotate any secrets on hosts that installed it.

Data as of 29 Oct 2026, 18:23 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-18072

What to do

Remove animatecss-tailwind-plugin from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmanimatecss-tailwind-plugin	Affected =2.0.6	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The animatecss-tailwind-plugin version 2.0.6 is a malicious Tailwind CSS plugin linked to a fake job interview campaign. It includes a private scoped dependency that requires an npm token to access, which delivers malicious code executed when the plugin loads in tailwind.config.js and the development server starts. The published package itself contains no install scripts or network code, and the malicious payload resides in the private dependency. Multiple similar malicious packages were published under various accounts over a recent period.

Impact

The malicious payload executes during the loading of the plugin in the development environment, potentially allowing execution of unauthorized code. However, the shipped package itself does not perform network communication or credential exfiltration directly. The threat relies on a private dependency accessible only with a committed npm token, which may limit exposure to users who use the compromised repository. The presence of multiple related malicious packages indicates a broader campaign targeting developers using npm packages.

Defensive guidance

Users should avoid using animatecss-tailwind-plugin version 2.0.6 and any related packages from the identified campaign. Since the malicious payload resides in a private dependency requiring an npm token, removing or not using the compromised plugin and its dependencies effectively mitigates the threat. There are no patches or fixes indicated; remediation involves removing the malicious packages from projects and registries. Monitor for any updates or advisories from npm or security vendors regarding this campaign.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 18:23 UTC

Technical details

References

Community reviews