Which versions of tailwind-form-templates are malicious?

The following npm versions of tailwind-form-templates are flagged malicious: 0.7.4. Treat any of these as compromised.

How do I remediate tailwind-form-templates if I installed it?

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

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

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

Malicious package

tailwind-form-templatesnpm

tailwind-form-templates is a confirmed malicious npm package (MAL-2026-13923) that steals credentials and exfiltrates sensitive data (malicious version 0.7.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-form-templates (npm)

MAL-2026-13923

Immediate action

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

npm uninstall tailwind-form-templates

What this malware does

The package name resembles @tailwindcss/forms and its src/index.js copies the legitimate @tailwindcss/forms source, appending an eval(atob(...)) payload that runs on require(). The decoded payload obfuscates its strings via \uXXXX escapes and dynamically requires http/https and child_process. At import time it queries Ethereum public RPCs and eth.blockscout.com/api for transactions from a hardcoded wallet (0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a), decodes an attacker-controlled IPv4 address from a transaction's to field, fetches an XOR-encrypted command from that IP via an x-payload-b64 header, and executes the result through eval and a detached spawn('node', ['-e',...]). This is a full-host remote code execution channel on the installer, with the C2 endpoint rotatable via on-chain transactions (EtherHiding pattern) and the malicious code grafted onto a legitimate library to evade casual review.

Malicious versions

1 flagged

0.7.4

Indicators of compromise (SHA-256)

8febe917c3076e12756acd284d92cd2810cb59f7c546a6e669ef23caa56457bc

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

Campaign

IN-MAL-2026-017619

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-form-templates-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