Which versions of json-mapping-token are malicious?

The following npm versions of json-mapping-token are flagged malicious: 2.2.4. Treat any of these as compromised.

How do I remediate json-mapping-token if I installed it?

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

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

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

Search your lockfiles and build artifacts for json-mapping-token (version 2.2.4).

Malicious package

json-mapping-tokennpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

json-mapping-token is a confirmed malicious npm package (MAL-2026-2368) that executes malicious code on install (malicious version 2.2.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in json-mapping-token (npm)

MAL-2026-2368

Immediate action

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

npm uninstall json-mapping-token

What this malware does

The package json-mapping-token was found to contain malicious code.

Malicious versions

1 flagged

2.2.4

Indicators of compromise (SHA-256)

1bcdb4507fd1a486a27de58d8edc2a2add4c73cabbd014ee373889836f8da30d

c3e27e1c4dcb0a7a03e552d242b6d13a6834ae89bf87382c9ff28d8e88820be8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01774

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks json-mapping-token-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