Which versions of jsonapptoken are malicious?

The following npm versions of jsonapptoken are flagged malicious: 2.3.8. Treat any of these as compromised.

How do I remediate jsonapptoken if I installed it?

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

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

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

Search your lockfiles and build artifacts for jsonapptoken (version 2.3.8).

Malicious package

jsonapptokennpm

Advisory published Dec 23, 2025Updated Mar 19, 2026

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

Malicious code in jsonapptoken (npm)

MAL-2025-192808

Immediate action

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

npm uninstall jsonapptoken

What this malware does

The package jsonapptoken was found to contain malicious code.

Malicious versions

1 flagged

2.3.8

Indicators of compromise (SHA-256)

124108675dd958b7dfed21505eaa7ceef8b50bb19ca1bac59f6b42b4e6633492

40b5e4f69790478de9df8bd2927408bf4ce006c71674885ae54dda73c140d8bb

dbbd1ae617522a1fe35503188626f9e4466aa53468e0a350b745ba62f0278585

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for jsonapptoken (version 2.3.8).
If you installed it — respond
Remove jsonapptoken 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 jsonapptoken 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. jsonapptoken on npm has been identified as a malicious package (version 2.3.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06374RLUA-2026-01371

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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