Which versions of react-malicious-clone are malicious?

The following npm versions of react-malicious-clone are flagged malicious: 19.3.0-canary-d5736f09-20260507. Treat any of these as compromised.

How do I remediate react-malicious-clone if I installed it?

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

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

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

Malicious package

react-malicious-clonenpm

react-malicious-clone is a confirmed malicious npm package (MAL-2026-4660) that steals credentials and exfiltrates sensitive data (malicious version 19.3.0-canary-d5736f09-20260507). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-malicious-clone (npm)

MAL-2026-4660

Immediate action

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

npm uninstall react-malicious-clone

What this malware does

Package name impersonates React and the package.json copies React's description, homepage (react.dev), bugs URL, and canary versioning scheme. On require/import, index.js synchronously collects os.hostname(), os.userInfo().username, cwd, platform, arch, node version, and iterates process.env filtering keys against /token|key|secret|password|auth|credential|api/i to capture arbitrary installer secrets (CI tokens, npm tokens, AWS keys, GitHub tokens, etc.). The resulting JSON payload is POSTed via https to webhook.site/0240f6ff-33e5-40a5-845a-8e3f80b6d957. The code self-labels '[SUPPLY CHAIN ATTACK - PoC]'. Any consumer requiring this package leaks credential-shaped environment variables to an attacker-controlled webhook.

Malicious versions

1 flagged

19.3.0-canary-d5736f09-20260507

Indicators of compromise (SHA-256)

b864ddf2d18e38ac791dd4fbacfa6fb37031ddb37538d91b3e0cebd472246b54

f03498aa5167e02289d4c8984282f6a1b6321af60fb9ff04d0ce9503faefffdd

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-004508IN-MAL-2026-004507

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-malicious-clone-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