NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

tailwind-form-corenpm

Advisory published Updated

tailwind-form-core is a confirmed malicious npm package (MAL-2026-18594) that typosquats a legitimate package to trick installs (malicious version 0.5.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-form-core (npm)

MAL-2026-18594
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tailwind-form-core

What this malware does

The package's declared main entry src/index.js begins with eval(atob('<~50KB base64 blob>')) that runs on every require/import. Decoding the string-array reveals node:http/https, node:child_process (spawn), '[eval]', stdin.write, and Ethereum RPC calls (eth_blockNumber, eth_getTransactionCount, eth_getBlockByNumber) issued to publicnode.com and drpc.org, plus Blockscout txlist queries ('/api?module=account&action=txlist'). The loader retrieves attacker-controlled payload data from these blockchain/dead-drop endpoints and executes it by piping into a spawned 'node -e' child process, yielding arbitrary code execution on the consumer host whenever the module is loaded. The payload destinations are concealed through obfuscator.io-style string-array + base64 wrapping with runtime index decoders (_0x5c1d/_0xa42d). The legitimate @tailwindcss/forms plugin source (plugin.withOptions(...)) is appended after the eval() so the package appears functional. package.json impersonates Tailwind Labs by falsifying repository to 'tailwindlabs/tailwindcss-forms' and author to '@tailwindcss', while the real package name 'tailwind-form-core' is a lookalike of the official '@tailwindcss/forms'.

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
0.5.5

Indicators of compromise (SHA-256)

c3a5d7c9b46c3501aae2d2ddeb597b15ad7d122180f8d7c7a961ab94ea96621e
982a885e35238eeb63f37a2d7e87eac99ff0eaad0514cd7f61778e5511694d01

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for tailwind-form-core (version 0.5.5).

  2. If you installed it — respond

    tailwind-form-core is a typosquat — you almost certainly intended a legitimately-named package. Remove tailwind-form-core, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If tailwind-form-core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tailwind-form-core on npm has been identified as a malicious package (version 0.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8cm5-g9p9-26frIN-MAL-2026-022540

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

tailwind-form-core (npm) malicious package — MAL-2026-18594 | O3 Security