Which versions of tailwindcss-hide-scrollbar are malicious?

The following npm versions of tailwindcss-hide-scrollbar are flagged malicious: 2.5.3, 2.5.4. Treat any of these as compromised.

How do I remediate tailwindcss-hide-scrollbar if I installed it?

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

I already installed tailwindcss-hide-scrollbar — how do I know if it already compromised me?

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

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

Malicious package

tailwindcss-hide-scrollbarnpm

tailwindcss-hide-scrollbar is a confirmed malicious npm package (MAL-2026-13424) that typosquats a legitimate package to trick installs (malicious versions 2.5.3, 2.5.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwindcss-hide-scrollbar (npm)

MAL-2026-13424

Immediate action

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

npm uninstall tailwindcss-hide-scrollbar

What this malware does

dist/index.js exports a small tailwind scrollbar-hide plugin followed by a trailing eval(atob('<~32KB obfuscator.io payload>')) that executes on every require()/import of the package. The decoded payload pulls in http, https, zlib and child_process.spawn (with require('child_proc'+'ess') split-string obfuscation and an obfuscator.io string-array dispatcher) and contains hardcoded Ethereum JSON-RPC method names (eth_getBlockByNumber, eth_blockNumber), etherscan-style transaction listing paths (?module=account&action=...&startblock=0&endblock=99999999), a process.env.ETH_RPC_URL read, and hardcoded RPC/explorer hosts under drpc.org, publicnode.com, blockscout.com and blast-api.io. A CSS utility plugin has no legitimate need for network I/O, spawned child processes, or dynamic evaluation of an obfuscated blob. The package name inverts the word order of the established tailwind-scrollbar-hide plugin, consistent with a typosquat carrier for the loader.

Malicious versions

2 flagged

2.5.32.5.4

Indicators of compromise (SHA-256)

1db817934d3c5903455ce642009849bbbfd95f40be9282d837615be21a288fab

ac906893a6ea1562025bfa35bf4f1998cfd745619f21c4dc3880aa386dc3cfe1

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-hide-scrollbar (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-hide-scrollbar across your stack and pipelines.
If you installed it — respond
tailwindcss-hide-scrollbar is a typosquat — you almost certainly intended a legitimately-named package. Remove tailwindcss-hide-scrollbar, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If tailwindcss-hide-scrollbar 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-hide-scrollbar 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-hide-scrollbar on npm has been identified as a malicious package (versions 2.5.3, 2.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016546IN-MAL-2026-016545

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-hide-scrollbar-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database