Which versions of json-mappings are malicious?

Every published version of json-mappings on npm is considered malicious. Remove the package entirely.

How do I remediate json-mappings if I installed it?

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

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

Yes — json-mappings is associated with the GHSA-jjf5-hhf5-4mcc 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-mappings 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-mappings (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging json-mappings across your stack and pipelines.

Malicious package

json-mappingsnpm

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

MAL-2026-160

Immediate action

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

npm uninstall json-mappings

What this malware does

The package json-mappings 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

f708e7c962688a26f87824a7ae962f667dc7238ba5b55aeb27c26e18c5f4b13f

5e1cd8f06a356d4ca69b87f0f2e2dbd6245d42c08c515189c1681251d0cf3aa3

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

Campaign

GHSA-jjf5-hhf5-4mcc

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks json-mappings-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