Critical Malicious Code Vulnerability in json-map-source Package

json-map-source Updated 05 Dec 2025

Summary

05/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192321: Malicious code in json-map-source (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The json-map-source package is a utility in the npm ecosystem designed for mapping JSON data structures. It is commonly used in web development to facilitate data manipulation and transformation. However, this package has been identified as containing malicious code, posing significant risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the json-map-source package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that any computer running this package should be considered fully compromised, leading to severe security implications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall json-map-source

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the json-map-source package and ensure that your system is secure.

Conclusion

The json-map-source package has been identified as containing malicious code, posing a significant threat to any system where it is installed. Immediate removal of the package and rotation of sensitive information is essential to mitigate the risks associated with this vulnerability.

See every vulnerability recorded for json-map-source →

Share this vulnerability

FAQ

You should uninstall the json-map-source package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Keeping this package installed can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

The best recovery method is to remove the package and rotate any compromised secrets or keys. Ensure your system is secure and monitor for any unusual activity.

While many npm packages are safe, it's essential to regularly monitor for vulnerabilities and use tools like Vulert to stay informed about potential risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall json-map-source

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback