MalwarePublished 19 Oct 2026Updated 29 Oct 2026

tailwind-animatecss-kit (npm) · Malicious Code

Affects tailwind-animatecss-kitSource GCVE Database

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

Data as of 29 Oct 2026, 17:54 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-18079

What to do

Remove tailwind-animatecss-kit 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
npmtailwind-animatecss-kit	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 npm package tailwind-animatecss-kit version 2.0.6 is associated with a malicious campaign involving fake job interviews. It includes a private scoped dependency that requires an npm token to resolve, enabling code execution when the plugin is loaded in tailwind.config.js and the development server starts. The public tarball itself contains no install scripts or network code, and no direct harmful code paths were identified in the shipped contents. Multiple similar packages were published under various accounts during mid-2026.

Impact

The malicious payload resides in a private dependency that requires an npm token to access, which means the code executes only in environments where this token is present (such as the lure repository). The public package itself does not contain harmful install-time or runtime code. There is no evidence of credential scraping, exfiltration endpoints, or obfuscated payloads in the public package. The threat is primarily relevant to users who inadvertently use the lure repository with the embedded npm token, potentially allowing execution of malicious code during development server startup.

Defensive guidance

Users should avoid installing tailwind-animatecss-kit version 2.0.6, especially from repositories that include private npm tokens or suspicious dependencies. Since the malicious payload is in a private dependency requiring a token, controlling access to npm tokens and auditing dependencies is critical. Monitor for updates from trusted sources regarding this campaign.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 17:54 UTC

Technical details

References

Community reviews