Which versions of tailwind-scrollbar-styles are malicious?

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

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

tailwind-scrollbar-styles 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-scrollbar-styles — how do I know if it already compromised me?

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

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

Malicious package

tailwind-scrollbar-stylesnpm

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

Malicious code in tailwind-scrollbar-styles (npm)

MAL-2026-15904

Immediate action

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

npm uninstall tailwind-scrollbar-styles

What this malware does

dist/index.js exports a small tailwind plugin and then runs eval(atob("Z2x...")) on an embedded base64 blob at module load time. The decoded loader queries Ethereum RPC endpoints (1rpc.io/eth, drpc.org, publicnode, blastapi.io) and Blockscout for the most recent transaction sent by hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, decodes four bytes of that transaction's to field into an IPv4 address, HTTP-GETs http://<decoded-ip>:443/0x/cls and http://<decoded-ip>:443/0x/ls, XOR-decodes the response with literal keys, and executes it via eval() and via a detached spawn("node", ["-e",...], {detached:true, stdio:"ignore", windowsHide:true}).unref(). After first execution the loader reads its own file, locates the eval(atob("Z2x... region, and rewrites dist/index.js with the region removed, so the malicious line disappears from disk. The Ethereum-transaction-based resolver lets the operator rotate the C2 IP at any time by publishing a new transaction from the controlling address, and the self-erasing stub defeats post-incident inspection of the installed copy.

Malicious versions

1 flagged

4.0.3

Indicators of compromise (SHA-256)

2c9c5760f878552d4d2aedb3afc283b64ba99e65acf1e086158afe79a0267ada

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-scrollbar-styles (version 4.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-scrollbar-styles across your stack and pipelines.
If you installed it — respond
tailwind-scrollbar-styles 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-scrollbar-styles 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-scrollbar-styles 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-scrollbar-styles on npm has been identified as a malicious package (version 4.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019449

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-scrollbar-styles-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