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?

jsonapptoken is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed jsonapptoken — how do I know if it already compromised me?

If jsonapptoken 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jsonapptoken (version 2.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonapptoken across your stack and pipelines.

Malicious package

jsonapptokennpm

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

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

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jsonapptoken (version 2.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsonapptoken across your stack and pipelines.
If you installed it — respond
jsonapptoken is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If jsonapptoken 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 jsonapptoken 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. 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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring