Which versions of react-linear-loader are malicious?

The following npm versions of react-linear-loader are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate react-linear-loader if I installed it?

react-linear-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed react-linear-loader — how do I know if it already compromised me?

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

Yes — react-linear-loader is associated with the GHSA-9rcr-762f-rfwj 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-linear-loader across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for react-linear-loader (version 1.0.2).

Malicious package

react-linear-loadernpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

react-linear-loader is a confirmed malicious npm package (MAL-2025-190993) that steals credentials and exfiltrates sensitive data (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-linear-loader (npm)

MAL-2025-190993

Immediate action

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

npm uninstall react-linear-loader

What this malware does

The package react-linear-loader was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

05d1d85db1e83ffa998cf1e9dbc57cda9efbc5d953baa2c57d68a4708c89936c

ccf5203f35299ba1826e76daefdfa5e28ce387072c612234ee91afa242ba8df5

8e9af52e869b966f68c14644ba508c66e9d2908279dab4984f869949748b7084

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for react-linear-loader (version 1.0.2).
If you installed it — respond
react-linear-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If react-linear-loader 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. react-linear-loader on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9rcr-762f-rfwj

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-linear-loader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database