Which versions of tailwind-plugin-kit are malicious?

The following npm versions of tailwind-plugin-kit are flagged malicious: 1.3.2. Treat any of these as compromised.

How do I remediate tailwind-plugin-kit if I installed it?

tailwind-plugin-kit 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-plugin-kit — how do I know if it already compromised me?

If tailwind-plugin-kit 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.

Is tailwind-plugin-kit part of a known attack campaign?

Yes — tailwind-plugin-kit is associated with the IN-MAL-2026-017759 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

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

Search your lockfiles and build artifacts for tailwind-plugin-kit (version 1.3.2).

Malicious package

tailwind-plugin-kitnpm

Advisory published Aug 14, 2026Updated Aug 14, 2026

tailwind-plugin-kit is a confirmed malicious npm package (MAL-2026-14037) that steals credentials and exfiltrates sensitive data (malicious version 1.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-plugin-kit (npm)

MAL-2026-14037

Immediate action

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

npm uninstall tailwind-plugin-kit

What this malware does

The package presents itself as a Tailwind CSS plugin toolkit but its exported getPlugin function performs an HTTPS request to a hardcoded bare-IP endpoint (31.97.137.157:45000/icons/109) and passes the response's data.credits field to new Function(...) with a full Node.js execution context (require, module, exports, process, Buffer, globalThis, Promise). Any project following the README instructions and registering the package as a Tailwind plugin (plugins: [toolkit]) triggers execution of arbitrary attacker-controlled JavaScript on the developer/build machine. The destination URL is assembled by concatenating separate protocol/domain/path fragments, and the file also contains an unused setDefaultModule referencing well-known CDN hostnames (cloudflare, fastly, akamai, cloudfront) as a decoy — the actual network destination is the bare IP, not any CDN. Declared dependencies (@primno/dpapi, better-sqlite3, node-machine-id) are consistent with a second-stage infostealer payload targeting browser credential stores and machine identifiers on the loaded host.

Malicious versions

1 flagged

1.3.2

Indicators of compromise (SHA-256)

3e480310d422f93f8558763cca56b726148c94b19e20eec879f0786c01c264af

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tailwind-plugin-kit (version 1.3.2).
If you installed it — respond
tailwind-plugin-kit 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-plugin-kit 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-plugin-kit on npm has been identified as a malicious package (version 1.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017759

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-plugin-kit-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