Which versions of json-map-source are malicious?

The following npm versions of json-map-source are flagged malicious: 2.3.7, 2.3.8. Treat any of these as compromised.

How do I remediate json-map-source if I installed it?

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

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

Yes — json-map-source is associated with the GHSA-qfx2-px7q-fq7c, RLMA-2025-06372, RLUA-2026-01366 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-map-source 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 json-map-source (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-map-source across your stack and pipelines.

Malicious package

json-map-sourcenpm

Malicious code in json-map-source (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192321

Immediate action

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

npm uninstall json-map-source

What this malware does

The package json-map-source was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

2.3.72.3.8

Indicators of compromise (SHA-256)

3c10e01cd8946f23f63e8eb210a0de73503e9815cf616aee78f18c96c4fe2ef0

6dd2d0607d185e9c26b9f948e2335066b6e537f3f192794f59fdf55548300006

741c8fd6bf6a0b0e779babcfccc9f35c6af37f632a03f46fde6ad05ceb07a1c4

9f28077aedceff25ea844f178ae414f6beb539b14440e550a0de1d37b50a76e7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for json-map-source (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-map-source across your stack and pipelines.
If you installed it — respond
Remove json-map-source 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-map-source 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 json-map-source 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. json-map-source on npm has been identified as a malicious package (versions 2.3.7, 2.3.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qfx2-px7q-fq7cRLMA-2025-06372RLUA-2026-01366

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks json-map-source-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