Which versions of scrollbar-hide-plugin are malicious?

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

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

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

If scrollbar-hide-plugin was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is scrollbar-hide-plugin part of a known attack campaign?

Yes — scrollbar-hide-plugin is associated with the IN-MAL-2026-014579 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 scrollbar-hide-plugin across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for scrollbar-hide-plugin (version 1.0.1).

Malicious package

scrollbar-hide-pluginnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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

Malicious code in scrollbar-hide-plugin (npm)

MAL-2026-12192

Immediate action

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

npm uninstall scrollbar-hide-plugin

What this malware does

The package's main entry (dist/index.js) appends an obfuscated payload — wrapped in eval(atob(...)) with require targets and URLs hidden in \uXXXX escapes — to an otherwise legitimate Tailwind scrollbar-hide plugin. When the package is required or imported, the payload queries Ethereum RPCs for transactions from a hardcoded address (0xa322e5f3d311d3080e6f0121063e9adc2490ef1a), decodes attacker IPv4 addresses from the transaction to field bytes, and fetches XOR-encoded JavaScript from those IPs on port 443 (paths /0x/cls and /0x/ls). The fetched code is then executed both via eval in-process and via spawn('node', ['-e',...], {detached:true}).unref() as a detached child process. The C2 destinations are resolved dynamically from on-chain data, so the operator can rotate infrastructure without republishing the package. The name resembles the legitimate tailwind-scrollbar-hide package (reslear/tailwind-scrollbar-hide), consistent with a name-squat trojan.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

4f19e1731b591552a096b108703702b9663c1bbb8cf9c2ff6fc048f8582e8607

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for scrollbar-hide-plugin (version 1.0.1).
If you installed it — respond
scrollbar-hide-plugin 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 scrollbar-hide-plugin was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. scrollbar-hide-plugin on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014579

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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