Which versions of jsonrecap are malicious?

The following npm versions of jsonrecap are flagged malicious: 3.1.8. Treat any of these as compromised.

How do I remediate jsonrecap if I installed it?

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

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

Yes — jsonrecap is associated with the RLMA-2025-06378, RLUA-2026-01378 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 jsonrecap 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 jsonrecap (version 3.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonrecap across your stack and pipelines.

Malicious package

jsonrecapnpm

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

MAL-2025-192812

Immediate action

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

npm uninstall jsonrecap

What this malware does

The package jsonrecap was found to contain malicious code.

Malicious versions

1 flagged

3.1.8

Indicators of compromise (SHA-256)

0f2988a1bf0dbfd6ff12cb50f4278ad710593f273f8e6e8b594f6d95081ca1aa

a7e3ea65451f642ffd038933f2ca3b5dab39d6ee6979b4783353af6250dc22e9

a41d1fcb63a586513d9cca8b1183243004470500c8db731516479b0a771a3dbb

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

Campaign

RLMA-2025-06378RLUA-2026-01378

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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