Which versions of jsonauto are malicious?

The following npm versions of jsonauto are flagged malicious: 5.1.0. Treat any of these as compromised.

How do I remediate jsonauto if I installed it?

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

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

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

Malicious package

jsonautonpm

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

MAL-2025-192811

Immediate action

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

npm uninstall jsonauto

What this malware does

The package jsonauto was found to contain malicious code.

Malicious versions

1 flagged

5.1.0

Indicators of compromise (SHA-256)

198cb8e37f235b885e0f26a594eccfa7749eb3b2f58e6f3f5015e215e6913c6e

ce9bf596900bc5133273dd4e77700e5636518a55c780b186e42a26d30efeabc3

3f1dd63edd30a6580f42521ca40336bcd96c58b30dc72ae6a2fa54c8e31e01d1

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

Campaign

RLMA-2025-06377RLUA-2026-01374

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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