Which versions of react-scroll-disable are malicious?

The following npm versions of react-scroll-disable are flagged malicious: 2.5.2. Treat any of these as compromised.

How do I remediate react-scroll-disable if I installed it?

react-scroll-disable 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 react-scroll-disable — how do I know if it already compromised me?

If react-scroll-disable 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 react-scroll-disable part of a known attack campaign?

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

Malicious package

react-scroll-disablenpm

react-scroll-disable is a confirmed malicious npm package (MAL-2026-12189) that opens a backdoor for remote access (malicious version 2.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-scroll-disable (npm)

MAL-2026-12189

Immediate action

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

npm uninstall react-scroll-disable

What this malware does

On require of react-scroll-disable, the package's main entry executes an eval(atob(...)) blob appended after the legitimate RemoveScroll export. The blob loads child_process and http via \uXXXX-escaped identifiers, queries public Ethereum RPCs for the latest transaction to address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, decodes the transaction's to field into two IPv4 addresses, and issues GET/HEAD requests to those hosts on port 443 (paths /0x/cls and /0x/ls). The response carries an XOR-encrypted second-stage script in an x-payload-b64 header, which is decrypted and executed via spawn('node', ['-e', <payload>], {detached: true, stdio: 'ignore', windowsHide: true}).unref(), producing a detached child process running attacker-controlled code with no user interaction. The same payload is present in both dist/es2015 and dist/es2019 entry files. The attacker rotates the delivery IP by publishing new on-chain transactions, so the fetched code changes without any package update.

Malicious versions

1 flagged

2.5.2

Indicators of compromise (SHA-256)

30e2eae248242fe92d777348542534e187d7773c2a092e8d3240d8bdd5b94afa

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

Campaign

IN-MAL-2026-014564

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-scroll-disable-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