Which versions of tailwindcss-form-components are malicious?

The following npm versions of tailwindcss-form-components are flagged malicious: 1.4.0, 1.4.1, 1.5.0, 1.5.1. Treat any of these as compromised.

How do I remediate tailwindcss-form-components if I installed it?

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

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

Yes — tailwindcss-form-components is associated with the IN-MAL-2026-014542, IN-MAL-2026-014543, IN-MAL-2026-014544, IN-MAL-2026-014545 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-form-components 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-form-components (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-form-components across your stack and pipelines.

Malicious package

tailwindcss-form-componentsnpm

tailwindcss-form-components is a confirmed malicious npm package (MAL-2026-12223) that steals credentials and exfiltrates sensitive data (malicious versions 1.4.0, 1.4.1, 1.5.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwindcss-form-components (npm)

MAL-2026-12223

Immediate action

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

npm uninstall tailwindcss-form-components

What this malware does

index.js exposes getPlugin(), which performs an HTTP GET to http://46.183.25.232:45000/icons/106, parses the JSON response, and passes the credits field to new Function(...) with require, module, process, and Buffer injected — giving the remote endpoint full Node.js execution privileges on the consumer's host. The destination URL is assembled from split string fragments (protocol/separator/domain/path) and framed with icon/CDN-style naming (iconDomain, bearrtoken: 'logo', path segment icons/), while a separate setDefaultModule function references a benign-looking cdnjs/font-awesome URL as a decoy. The package name typosquats the tailwindcss ecosystem, and declared dependencies include @primno/dpapi, better-sqlite3, and node-machine-id — libraries associated with Windows credential/DPAPI access, browser SQLite database reads, and host fingerprinting. The transport is plain HTTP to a bare IP with no integrity check, so the executed payload is attacker-controlled and mutable.

Malicious versions

4 flagged

1.4.01.4.11.5.01.5.1

Indicators of compromise (SHA-256)

1303bc98b90034a6704873e88f11f33207f609c31f8077ed5ae380cf31b10f04

ae9425c630e8b36b03993f6124066f178a86a285ae44e5e4590016ac575c4cac

393ff15b40cda09a0b32deb99d0cd7448549b9d9d720441ab927e79254fe9230

727102c57f82c9751430045ef877b326a641f3b69d9d1f9a4571918b264de027

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

Campaign

IN-MAL-2026-014542IN-MAL-2026-014543IN-MAL-2026-014544IN-MAL-2026-014545

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-form-components-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