Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

json-merge-toolnpm

Malicious code in json-merge-tool (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1297
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall json-merge-tool

What this malware does

The package json-merge-tool 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

1 flagged
2.1.1

Indicators of compromise (SHA-256)

4bb041118bdac1123bd722a9b1f99ddb6ca406f7ce80d5de344b2c36614b89e9
f16e8d9c37feb30d5a44f7a94620c3a09d182a34cd5ccc1e7c97aaf4a991ab10
573d54372e591af2f5a25153f677feed589f98f0da62aef9c3bcc5afec37d1ae

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for json-merge-tool (version 2.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-merge-tool across your stack and pipelines.

  2. If you installed it — respond

    Remove json-merge-tool 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.

  3. Did it already run?

    If json-merge-tool 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.

  4. How O3 protects you

    O3 blocks json-merge-tool 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. json-merge-tool on npm has been identified as a malicious package (version 2.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cpf2-rx79-x333RLMA-2026-01775

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks json-merge-tool-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.

json-merge-tool (npm) malicious package — MAL-2026-1297 | O3 Security