Which versions of tailwindcss-forms-bundler are malicious?

Every published version of tailwindcss-forms-bundler on npm is considered malicious. Remove the package entirely.

How do I remediate tailwindcss-forms-bundler if I installed it?

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

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

Yes — tailwindcss-forms-bundler is associated with the GHSA-gm2h-wf73-fxx5 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-forms-bundler 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-forms-bundler (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-forms-bundler across your stack and pipelines.

Malicious package

tailwindcss-forms-bundlernpm

Malicious code in tailwindcss-forms-bundler (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1336

Immediate action

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

npm uninstall tailwindcss-forms-bundler

What this malware does

The package tailwindcss-forms-bundler was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

ce8e85d706477513dec4568dffb1ffad1e08f8fc590cbd827b5a97f26b47a1a8

4539095c0f138c7afdd678f16ce6331acda209486c0e8ebe9f156da96b5de11a

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-forms-bundler (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-forms-bundler across your stack and pipelines.
If you installed it — respond
Remove tailwindcss-forms-bundler 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-forms-bundler 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-forms-bundler 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-forms-bundler on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gm2h-wf73-fxx5

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-forms-bundler-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