Which versions of json-mapping-sources are malicious?

The following npm versions of json-mapping-sources are flagged malicious: 2.4.3, 2.4.5, 2.4.7. Treat any of these as compromised.

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

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

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

Yes — json-mapping-sources is associated with the GHSA-vphr-h9xh-66ff, RLMA-2026-01367 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-sources 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-mapping-sources (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-mapping-sources across your stack and pipelines.

Malicious package

json-mapping-sourcesnpm

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

MAL-2026-819

Immediate action

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

npm uninstall json-mapping-sources

What this malware does

The package json-mapping-sources 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

3 flagged

2.4.32.4.52.4.7

Indicators of compromise (SHA-256)

b0cfae2b7882c75ea6f086dd86990859edb1ee371ad88cf1b0bdbc3ed2de7159

77824e69a815d8ac27a50bb52fa0a39fe2c7e512e6597d3aefd500b0eae847e8

3dadda660eeab3333d02be6252d9edf924c69a05e2a819fa27e891fb221060ff

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-mapping-sources (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-mapping-sources across your stack and pipelines.
If you installed it — respond
Remove json-mapping-sources 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-sources 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-mapping-sources 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-mapping-sources on npm has been identified as a malicious package (versions 2.4.3, 2.4.5, 2.4.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vphr-h9xh-66ffRLMA-2026-01367

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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