Critical Malicious Code Vulnerability in json-mapping-source Package

json-mapping-source Updated 06 Feb 2026

Summary

04/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-725: Malicious code in json-mapping-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 Penetration testing for web, API and mobile 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-mapping-source package is a library used in Node.js applications for mapping JSON data structures. It is commonly utilized in various projects for data transformation and manipulation. However, this package has been found to contain malicious code, posing significant security risks to any application that integrates it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the json-mapping-source package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it embeds harmful functionalities that can lead to severe security breaches.

How To Fix

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

npm uninstall json-mapping-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

As a temporary workaround, you can isolate the application from the internet and limit access to sensitive data until the package is removed and the system is secured. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The json-mapping-source package has been identified as containing malicious code, which poses a significant risk to any system using it. Immediate action is required to remove the package and secure any compromised data. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for json-mapping-source →

Share this vulnerability

FAQ

Immediately remove the json-mapping-source package from your project and rotate any secrets or keys that may have been compromised.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, complete system compromise, and potential data breaches.

Yes, tools like Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

While many packages on npm are safe, it is essential to regularly audit your dependencies and stay informed about vulnerabilities to mitigate risks.

How To Fix

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

npm uninstall json-mapping-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