Critical Malicious Code Vulnerability in json-mapping-srcs Package

json-mapping-srcs Updated 24 Feb 2026

Summary

24/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1017: Malicious code in json-mapping-srcs (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The json-mapping-srcs package is an npm library designed for mapping JSON data sources. It is commonly used in web applications to facilitate data manipulation and integration. However, this package has been identified as containing malicious code, which poses a significant security risk to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the json-mapping-srcs package. This code can compromise any computer that has the package installed, granting unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to complete control of the affected system by an external entity. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall json-mapping-srcs

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-mapping-srcs package and secure your system.

Conclusion

The json-mapping-srcs package contains malicious code that poses a serious security threat. Users must uninstall the package immediately and take steps to secure their systems. Regular monitoring for vulnerabilities using tools like Vulert is recommended to maintain security in open-source projects.

See every vulnerability recorded for json-mapping-srcs →

Share this vulnerability

FAQ

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

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

Keeping this package installed poses a significant risk as it can allow attackers to gain unauthorized access to your system and sensitive data.

No, there is currently no patched version available for the json-mapping-srcs package. The only safe action is to uninstall it.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

How To Fix

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

npm uninstall json-mapping-srcs

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