Which versions of jsonify-errors are malicious?

The following npm versions of jsonify-errors are flagged malicious: 3.6.9, 3.7.0. Treat any of these as compromised.

How do I remediate jsonify-errors if I installed it?

Remove jsonify-errors from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed jsonify-errors — how do I know if it already compromised me?

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

Yes — jsonify-errors is associated with the GHSA-4hp4-98m6-767r, RLMA-2026-01376 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 jsonify-errors 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 jsonify-errors (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonify-errors across your stack and pipelines.

Malicious package

jsonify-errorsnpm

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

MAL-2025-192384

Immediate action

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

npm uninstall jsonify-errors

What this malware does

The package jsonify-errors was found to contain malicious code.

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

2 flagged

3.6.93.7.0

Indicators of compromise (SHA-256)

756f389321cc3f827ceaff0d493d6792c81f6b2917bb67890f07c81dc6f64b1d

f4b6594184587f6475f55e2b97c6f1af77e43da5026cc23d96dec6cfc70c1537

d71ee425f08eae64b4a2ab4e31f9b10a9fc9b70d518d07a9e275832217ff919c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jsonify-errors (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonify-errors across your stack and pipelines.
If you installed it — respond
Remove jsonify-errors from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If jsonify-errors 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 jsonify-errors 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. jsonify-errors on npm has been identified as a malicious package (versions 3.6.9, 3.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4hp4-98m6-767rRLMA-2026-01376

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks jsonify-errors-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring