Which versions of json-mapping-fetch are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for json-mapping-fetch (version 2.4.3).

Malicious package

json-mapping-fetchnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

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

Malicious code in json-mapping-fetch (npm)

MAL-2026-2367

Immediate action

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

npm uninstall json-mapping-fetch

What this malware does

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

Malicious versions

1 flagged

2.4.3

Indicators of compromise (SHA-256)

bf6089bb1ca878bef887466d0f4de52313a31360ef59f6bba682b579bad28936

45649188d792a4c0d12add7ece8a5f8bd1f35ea2478d963b75238249cc788de3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01773

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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