Which versions of jsondatahandle are malicious?

The following npm versions of jsondatahandle are flagged malicious: 1.999.0. Treat any of these as compromised.

How do I remediate jsondatahandle if I installed it?

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

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

Yes — jsondatahandle is associated with the RLMA-2026-01375 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 jsondatahandle across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jsondatahandle (version 1.999.0).

Malicious package

jsondatahandlenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

jsondatahandle is a confirmed malicious npm package (MAL-2026-1757) that executes malicious code on install (malicious version 1.999.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jsondatahandle (npm)

MAL-2026-1757

Immediate action

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

npm uninstall jsondatahandle

What this malware does

The package jsondatahandle was found to contain malicious code.

Malicious versions

1 flagged

1.999.0

Indicators of compromise (SHA-256)

4008e807ce3be5ebef9b9a5d35c15ae5db600fcac16f89c022ed7825c77769c0

4b6e1e8667e2553903eb45d7c1a70b91d129e453052228aca018fc7508d64f09

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01375

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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