Which versions of tailwind-aspect are malicious?

The following npm versions of tailwind-aspect are flagged malicious: 0.4.2. Treat any of these as compromised.

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

tailwind-aspect is a typosquat — you almost certainly intended a legitimately-named package. Remove tailwind-aspect, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If tailwind-aspect 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 tailwind-aspect part of a known attack campaign?

Yes — tailwind-aspect is associated with the IN-MAL-2026-019478 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-aspect 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 tailwind-aspect (version 0.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-aspect across your stack and pipelines.

Malicious package

tailwind-aspectnpm

tailwind-aspect is a confirmed malicious npm package (MAL-2026-15912) that typosquats a legitimate package to trick installs (malicious version 0.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-aspect (npm)

MAL-2026-15912

Immediate action

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

npm uninstall tailwind-aspect

What this malware does

The package's main entrypoint unconditionally downloads a JavaScript file from the hardcoded plain-HTTP bare-IP URL http://23.27.245.100/index.js, writes it to./inout.js, and require()s it every time a consumer imports the package. The fetched content is unpinned, unverified, and served over cleartext HTTP, giving the operator of that IP (and any on-path attacker) arbitrary code execution on the installer's machine at import time. The package name and repository metadata impersonate the official @tailwindcss/aspect-ratio plugin (repository points at tailwindlabs/tailwindcss-aspect-ratio), providing cover for the loader; the remote fetch has no relationship to any Tailwind plugin functionality.

Malicious versions

1 flagged

0.4.2

Indicators of compromise (SHA-256)

e6ba6037f5f2f65c0ceef0ba5bd8da931b7860a85e7a38fb2703ad4cd7672ddf

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwind-aspect (version 0.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-aspect across your stack and pipelines.
If you installed it — respond
tailwind-aspect is a typosquat — you almost certainly intended a legitimately-named package. Remove tailwind-aspect, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If tailwind-aspect 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 tailwind-aspect 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. tailwind-aspect on npm has been identified as a malicious package (version 0.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019478

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-aspect-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