tw-fluid-typenpm
tw-fluid-type is a confirmed malicious npm package (MAL-2026-5638) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tw-fluid-type (npm)
What this malware does
The package advertises itself as a Tailwind CSS fluid-type plugin but ships src/utils/lib.min.js, which is loaded as a side effect when the package's main entry point is required. createClasses.js (reached from src/index.js) does const lib = require('./lib.min.js') and never uses the returned value — the only purpose of the require is to trigger the file's IIFE. lib.min.js caches global.r = require and global.m = module, then runs a ~4KB string through a custom Fisher-Yates-style deterministic shuffle (function YWG, seed 2540575) to decode JavaScript source, resolves the Function constructor via an obfuscated property lookup (YWG['constructor']), and invokes Function(...)(decoded_body) to execute the decoded code with full access to the cached require/module. A declarative CSS-utility plugin has no legitimate need to construct functions from shuffled-string blobs, cache require/module on the global object, or conceal its executable logic with a custom shuffle. Any consumer who imports this package executes the concealed payload at module load.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tw-fluid-type (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tw-fluid-type across your stack and pipelines.
If you installed it — respond
Remove tw-fluid-type 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 tw-fluid-type 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 tw-fluid-type 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tw-fluid-type-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.