Which versions of jsonauthcap are malicious?

The following npm versions of jsonauthcap are flagged malicious: 7.2.7. Treat any of these as compromised.

How do I remediate jsonauthcap if I installed it?

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

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

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

Malicious package

jsonauthcapnpm

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

MAL-2025-192810

Immediate action

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

npm uninstall jsonauthcap

What this malware does

The package jsonauthcap was found to contain malicious code.

Malicious versions

1 flagged

7.2.7

Indicators of compromise (SHA-256)

a4114af551ace62f174d96fabc6f6aed893fdeff7c2b07f7f8bd0c96699eb1b1

9dc3cf4a42e484d8f5f45422c109e11752cd6a37179357c39c8e3ce8b65e0b46

e69edf627c2d9d4cec636e78cb878edbc8025c59e0d50d53aa14b1a32f316811

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

Campaign

RLMA-2025-06376RLUA-2026-01373

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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