Which versions of tailwindcss-contact-form are malicious?

The following npm versions of tailwindcss-contact-form are flagged malicious: 0.5.1. Treat any of these as compromised.

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

tailwindcss-contact-form establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed tailwindcss-contact-form — how do I know if it already compromised me?

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

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

Malicious package

tailwindcss-contact-formnpm

tailwindcss-contact-form is a confirmed malicious npm package (MAL-2026-16251) that opens a backdoor for remote access (malicious version 0.5.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwindcss-contact-form (npm)

MAL-2026-16251

Immediate action

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

npm uninstall tailwindcss-contact-form

What this malware does

Package presents itself as the Tailwind CSS forms plugin (README is a verbatim copy of @tailwindcss/forms and its package.json points at github.com/tailwindlabs/tailwindcss-forms), and the README instructs users to require('tailwindcss-contact-form') from their tailwind.config.js. The single main file src/index.js is heavily obfuscated (obfuscator.io-style rotated string array, hex identifiers, control-flow flattening) and, when required, imports node:http/node:https and spawn from node:child_process, queries public Ethereum RPCs (eth.drpc.org, ethereum-rpc.publicnode.com, 1rpc.io/eth, public.blastapi.io) and the Blockscout txlist API for outbound transactions of the hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, extracts a base64 payload from transaction data (x-payload-B64), and executes it by spawning node. This is a remote-code-execution loader using the Ethereum blockchain as a command-and-control channel: whoever controls the hardcoded key controls code execution on every machine that imports the package. The Tailwind-forms cover story, verbatim README, and forged repository link exist to trick developers into wiring the require() into their build config.

Malicious versions

1 flagged

0.5.1

Indicators of compromise (SHA-256)

0b198bc6d5af472f9cb1f1db25acf0215b77c04a742fcce81fef5565d76d837b

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-contact-form (version 0.5.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-contact-form across your stack and pipelines.
If you installed it — respond
tailwindcss-contact-form establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If tailwindcss-contact-form 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-contact-form 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-contact-form on npm has been identified as a malicious package (version 0.5.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020120

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-contact-form-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database