Which versions of tailwind-hide-scrollbar are malicious?

The following npm versions of tailwind-hide-scrollbar are flagged malicious: 2.1.5. Treat any of these as compromised.

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

tailwind-hide-scrollbar 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.

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

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

Yes — tailwind-hide-scrollbar is associated with the IN-MAL-2026-013433, GHSA-97j6-7w7w-7vj3 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-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 tailwind-hide-scrollbar (version 2.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-hide-scrollbar across your stack and pipelines.

Malicious package

tailwind-hide-scrollbarnpm

tailwind-hide-scrollbar is a confirmed malicious npm package (MAL-2026-12116) that opens a backdoor for remote access (malicious version 2.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-hide-scrollbar (npm)

MAL-2026-12116

Immediate action

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

npm uninstall tailwind-hide-scrollbar

What this malware does

dist/index.js appends an eval(atob('...')) payload after the legitimate export default scrollbarHide; line. The decoded payload queries Ethereum RPC endpoints (eth.blockscout.com/api, 1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io) for the latest transaction from hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, interprets bytes of the to field as IPv4 addresses, HTTP GETs http://<ip>:443/0x/cls and http://<ip>:443/0x/ls, XOR-decrypts the responses, then evals the first stage and spawn('node', ['-e', payload], {detached:true, stdio:'ignore', windowsHide:true}).unref() to run the second stage detached. Inner strings such as child_process, http, https, spawn, and User-Agent are stored as \uXXXX unicode escapes to defeat static grep, wrapped in an outer base64 blob. The payload fires when any consumer imports the package, granting full Node-level remote code execution on the installer's host; the on-chain C2 resolution (EtherHiding) makes the destination attacker-mutable and resistant to takedowns.

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

2.1.5

Indicators of compromise (SHA-256)

cb0348430af0110be6ac537a38b5bb98983ec6b6f8f1474778ff16e4a4f4e8d8

982fe4a221da9b1452c033aeb2bf4472aff7fe03166d6874abc2d3162ba8998b

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwind-hide-scrollbar (version 2.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-hide-scrollbar across your stack and pipelines.
If you installed it — respond
tailwind-hide-scrollbar 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 tailwind-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 tailwind-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. tailwind-hide-scrollbar on npm has been identified as a malicious package (version 2.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-013433GHSA-97j6-7w7w-7vj3

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-hide-scrollbar-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database