Which versions of jsonauth are malicious?

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

How do I remediate jsonauth if I installed it?

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

If jsonauth was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is jsonauth part of a known attack campaign?

Yes — jsonauth is associated with the RLMA-2025-06375, RLUA-2026-01372 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 jsonauth across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jsonauth (version 7.2.7).

Malicious package

jsonauthnpm

Advisory published Dec 23, 2025Updated Mar 19, 2026

jsonauth is a confirmed malicious npm package (MAL-2025-192809) that executes malicious code on install (malicious version 7.2.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jsonauth (npm)

MAL-2025-192809

Immediate action

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

npm uninstall jsonauth

What this malware does

The package jsonauth was found to contain malicious code.

Malicious versions

1 flagged

7.2.7

Indicators of compromise (SHA-256)

b2e15ac6855d8cfed97e7774f58a71cfa204f0ef1da5d7c8956261b991a83e73

6e3fccdac696d746d016d5baa43d1ccd9475daced2fe66c37adb172f91a78c68

93c7d2298ad4d2edebf784691fb20536f2cb3985befe246bb26409bee2e201ba

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for jsonauth (version 7.2.7).
If you installed it — respond
Remove jsonauth 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 jsonauth was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. jsonauth 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-06375RLUA-2026-01372

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database