Which versions of tailwindcss-3d-styles are malicious?

The following npm versions of tailwindcss-3d-styles are flagged malicious: 1.2.4. Treat any of these as compromised.

How do I remediate tailwindcss-3d-styles if I installed it?

Remove tailwindcss-3d-styles from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed tailwindcss-3d-styles — how do I know if it already compromised me?

If tailwindcss-3d-styles was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is tailwindcss-3d-styles part of a known attack campaign?

Yes — tailwindcss-3d-styles is associated with the IN-MAL-2026-019456 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 tailwindcss-3d-styles across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-3d-styles (version 1.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-3d-styles across your stack and pipelines.

Malicious package

tailwindcss-3d-stylesnpm

tailwindcss-3d-styles is a confirmed malicious npm package (MAL-2026-15905) that executes malicious code on install (malicious version 1.2.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwindcss-3d-styles (npm)

MAL-2026-15905

Immediate action

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

npm uninstall tailwindcss-3d-styles

What this malware does

The package's main entry point fetches a JavaScript file from http://23.27.245.100:3000/index.js over plain HTTP at require time, writes the response to./inout.js in the current working directory, and require()s the resulting file — causing arbitrary code from that host to execute in the Node process of any consumer importing this package. The remaining code is a copy of the legitimate tailwindcss-3d library (per the manifest's repository/homepage), and the published name tailwindcss-3d-styles differs from the upstream tailwindcss-3d, using the upstream library as cover for the appended dropper.

Malicious versions

1 flagged

1.2.4

Indicators of compromise (SHA-256)

6afb2de10208993a1e7511cb81a6f11806561b389673da3fa24d22598178b744

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-3d-styles (version 1.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-3d-styles across your stack and pipelines.
If you installed it — respond
Remove tailwindcss-3d-styles from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tailwindcss-3d-styles was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tailwindcss-3d-styles before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. tailwindcss-3d-styles on npm has been identified as a malicious package (version 1.2.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019456

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-3d-styles-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database