Which versions of tailwind-kinetic are malicious?

The following npm versions of tailwind-kinetic are flagged malicious: 2.0.6, 2.0.8. Treat any of these as compromised.

How do I remediate tailwind-kinetic if I installed it?

tailwind-kinetic is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tailwind-kinetic — how do I know if it already compromised me?

If tailwind-kinetic was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find tailwind-kinetic across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tailwind-kinetic (2 malicious versions).

Malicious package

tailwind-kineticnpm

Advisory published Oct 19, 2026Updated Oct 20, 2026

tailwind-kinetic is a confirmed malicious npm package (MAL-2026-18084) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.6, 2.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-kinetic (npm)

MAL-2026-18084

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tailwind-kinetic

What this malware does

tailwind-kinetic (2.0.6, 2.0.8) is a Tailwind CSS plugin from the fake job interview campaign behind MAL-2026-17665 and MAL-2026-17666: the same Animate.css integration template, README and description, published by keinsell-jh on 2026-09-28. src/motion.js:5 requires the private scoped package @aaron205whitmore/postcss-animate-utils, which is not readable on the public registry and resolves only with the npm token committed in the lure repository's web/.npmrc, so the code it delivers runs when tailwind.config.js loads the plugin and the dev server starts. The published tarball contains no install scripts and no network code; the payload lives in the private dependency, which was not retrieved. Twenty-six such packages under seventeen accounts were published between 2026-07-28 and 2026-10-09.

Malicious versions

2 flagged

2.0.62.0.8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tailwind-kinetic (2 malicious versions).
If you installed it — respond
tailwind-kinetic is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tailwind-kinetic was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tailwind-kinetic on npm has been identified as a malicious package (versions 2.0.6, 2.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

pkgwarden · finder

Detect & block this

O3 blocks tailwind-kinetic-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database