Which versions of core-tailwindcss-utility are malicious?

The following npm versions of core-tailwindcss-utility are flagged malicious: 3.7.1. Treat any of these as compromised.

How do I remediate core-tailwindcss-utility if I installed it?

core-tailwindcss-utility 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 core-tailwindcss-utility — how do I know if it already compromised me?

If core-tailwindcss-utility 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 core-tailwindcss-utility part of a known attack campaign?

Yes — core-tailwindcss-utility is associated with the IN-MAL-2026-017984 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 core-tailwindcss-utility across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for core-tailwindcss-utility (version 3.7.1).

Malicious package

core-tailwindcss-utilitynpm

core-tailwindcss-utility is a confirmed malicious npm package (MAL-2026-14118) that steals credentials and exfiltrates sensitive data (malicious version 3.7.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in core-tailwindcss-utility (npm)

MAL-2026-14118

Immediate action

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

npm uninstall core-tailwindcss-utility

What this malware does

Package is advertised as a Tailwind CSS utility but ships no CSS utilities. index.js exports getPlugin() which fetches JSON from the hardcoded bare-IP endpoint https://31.97.137.157:45000/icons/108 and passes the response's credits field to new Function(...) with require, process, and Buffer bound in scope, executing the returned string as Node.js code on the caller's host. A decoy setDefaultModule() constructs cdnjs.<provider> URLs (cloudflare.com, fastly.net, etc.) to disguise the module as a font-awesome/CDN helper, but the actually-invoked path targets the bare-IP C2. Declared dependencies (@primno/dpapi for Windows DPAPI decryption, better-sqlite3/sqlite3, node-machine-id, socket.io-client, axios) are inconsistent with the stated Tailwind purpose and pre-stage the second-stage payload with primitives for browser credential decryption and remote C2, which the fetched code can load via the bound require.

Malicious versions

1 flagged

3.7.1

Indicators of compromise (SHA-256)

67bbda0dc4bcf5478f2edd6a243b1f289f2b0471f950b4362f21b5a6344cdd83

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-017984

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks core-tailwindcss-utility-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