Which versions of react-cleaner are malicious?

The following npm versions of react-cleaner are flagged malicious: 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate react-cleaner if I installed it?

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

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

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

Malicious package

react-cleanernpm

Malicious code in react-cleaner (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4791

Immediate action

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

npm uninstall react-cleaner

What this malware does

[email protected] is a pino-logger impersonator (package main is pino.js, homepage https://getpino.io, module layout mirrors pino's lib/ tree) that, on require, executes attacker-controlled remote code with the installer's environment in scope. lib/writer.js calls axios.get('https://www.jsonkeeper.com/b/MYUKZ') and passes the response body directly to eval(). jsonkeeper.com is a mutable paste-style host, so the author can rotate the executed payload at any time without republishing. Before the fetch, writer.js assembles a data object containing the entirety of process.env, os.hostname(), os.userInfo().username, os.platform(), and the host's non-internal MAC addresses; this object is in scope when the remote payload runs, giving the attacker direct access to AWS_*, GITHUB_TOKEN, NPM_TOKEN, and any other secrets present in the installer's environment. A second remote-code channel is hex-obfuscated alongside the plaintext one: a hl array decodes to 'axios','get','https://www.jsonkeeper.com/b/HY6M6','then', confirming deliberate concealment of a backup eval source. The combination — pino impersonation as cover, require-time fetch-and-eval from a mutable anonymous host, bulk env scrape staged in eval scope, hex-obfuscated secondary URL — is an unambiguous credential-harvesting RCE.

Malicious versions

2 flagged

1.0.41.0.5

Indicators of compromise (SHA-256)

11c3d7a072dc204b4c150fae46302a31dafd46c85518d4ba7128fc7d36bf6a53

31dbdda8b67e0d3fd9b3d5724d27f3451c558a33fd2fb4051fad460e78dc6bbf

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

Campaign

IN-MAL-2026-004873IN-MAL-2026-004877

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-cleaner-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