Which versions of tailwind-aspect-styles are malicious?

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

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

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

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

Yes — tailwind-aspect-styles is associated with the IN-MAL-2026-019722 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-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 tailwind-aspect-styles (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-styles across your stack and pipelines.

Malicious package

tailwind-aspect-stylesnpm

tailwind-aspect-styles is a confirmed malicious npm package (MAL-2026-16056) that executes malicious code on install (malicious version 0.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-aspect-styles (npm)

MAL-2026-16056

Immediate action

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

npm uninstall tailwind-aspect-styles

What this malware does

The package's main module (src/index.js) performs an https.get to http://23.27.245.100/index.js over plain HTTP, writes the response to./inout.js in the consumer's working directory, and immediately require()s the written file. The fetch is unpinned, unauthenticated, and served from a bare IP over cleartext, so the operator of that endpoint controls arbitrary JavaScript executed in the Node process that loads this package. The package presents itself as the Tailwind aspect-ratio plugin, with a package.json repository field pointing to tailwindlabs/tailwindcss-aspect-ratio, while the dropper is appended after the legitimate-looking plugin export.

Malicious versions

1 flagged

0.4.2

Indicators of compromise (SHA-256)

4d63fe1e50dc7d704732a5e92e95f320fcc3fac45c5a0a223ed278f316c2bb14

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 tailwind-aspect-styles (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-styles across your stack and pipelines.
If you installed it — respond
Remove tailwind-aspect-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 tailwind-aspect-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 tailwind-aspect-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. tailwind-aspect-styles 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-019722

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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