Which versions of tailwind-elements-ui are malicious?

The following npm versions of tailwind-elements-ui are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate tailwind-elements-ui if I installed it?

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

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

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

Malicious package

tailwind-elements-uinpm

tailwind-elements-ui is a confirmed malicious npm package (MAL-2026-13727) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-elements-ui (npm)

MAL-2026-13727

Immediate action

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

npm uninstall tailwind-elements-ui

What this malware does

No malicious behavior was identified in the package contents. The package name resembles popular Tailwind-related UI libraries, which can indicate name-confusion risk, but no exfiltration, dropper, silent-relay, credential distribution, or install-time remote code execution was observed in the inspected files. Routing to human review so a reviewer can assess name-confusion risk and confirm the package's stated purpose against its contents.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

630411d10962acda78d9009d4ce6af7df02639cc3f8785c4c07acdfa06fdca36

75f8605cff87e89b9f1a50c65fc27af278335cf414a8b4fb52ea4090e9fdd71b

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwind-elements-ui (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-elements-ui across your stack and pipelines.
If you installed it — respond
tailwind-elements-ui 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-elements-ui 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-elements-ui 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-elements-ui on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mmpq-4w6p-rwg2IN-MAL-2026-017310

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-elements-ui-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