Critical Malicious Code Vulnerability in jsonify-setting Package

jsonify-setting Updated 08 Jan 2026

Summary

08/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-161: Malicious code in jsonify-setting (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 jsonify-setting package is an npm module designed for JSON manipulation and formatting. It is commonly used in JavaScript applications to streamline the process of handling JSON data. However, this package has been identified to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the jsonify-setting package. This code can grant unauthorized access to the system, allowing attackers to control the affected computer fully. The implications are severe, as any secrets or keys stored on the compromised machine may be exposed. Users are advised to treat any system running this package as fully compromised and take immediate action to secure their data.

How To Fix

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

npm uninstall jsonify-setting

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 workaround, if you cannot immediately remove the package, consider isolating the affected application from sensitive data and networks until the package can be safely removed.

Conclusion

The jsonify-setting package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for jsonify-setting →

Share this vulnerability

FAQ

Immediately remove the package and rotate any secrets or keys 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.

Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation of sensitive information.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall jsonify-setting

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