tailwindcss-scrollbar-hidenpm
tailwindcss-scrollbar-hide is a confirmed malicious npm package (MAL-2026-12224) that opens a backdoor for remote access (malicious version 2.2.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tailwindcss-scrollbar-hide (npm)
What this malware does
dist/index.js appends eval(atob('...')) after the legitimate CSS-plugin export, so simply importing or requiring the package executes an obfuscated payload on the installer's machine. Identifiers in the payload (http, https, child_process, spawn, hostnames, RPC method names) are hidden with \u00XX escapes. The decoded payload queries Ethereum public RPCs (1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io) and eth.blockscout.com for the latest transaction from the attacker-controlled address 0xa322E5f3D311D3080e6f01210763e9aDC2490Ef1a, treats the first 8 bytes of that transaction's to field as two IPv4 addresses, fetches second-stage bytes from http://<ip>:443/0x/cls and http://<ip>:443/0x/ls, XOR-decodes them, and runs them via eval and a detached spawn('node', ['-e',...], {detached: true, stdio: 'ignore', windowsHide: true}).unref(). The advertised purpose is a zero-dependency pure-CSS Tailwind plugin; the presence of network, child_process, blockchain lookup, obfuscation, and dynamic code execution in that context has no legitimate purpose. The on-chain dead-drop lookup lets the operator rotate the C2 endpoint at will by broadcasting new transactions from the watched address.
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
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-scrollbar-hide (version 2.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-scrollbar-hide across your stack and pipelines.
If you installed it — respond
tailwindcss-scrollbar-hide 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-scrollbar-hide 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-scrollbar-hide 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 tailwindcss-scrollbar-hide-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.