Critical Malicious Code Vulnerability in jsonify-settings Package
Summary
MAL-2025-192307: Malicious code in jsonify-settings (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The jsonify-settings package is an npm library designed to facilitate the management of JSON settings in applications. It allows developers to easily configure and manipulate settings stored in JSON format. However, this package has been compromised, leading to severe security risks for any application utilizing it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the jsonify-settings package. This malicious code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has injected harmful code into the package, making it a significant threat to users and their systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jsonify-settingsIf 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, ensure that you do not use the jsonify-settings package in your projects. Instead, consider alternative libraries that provide similar functionality without the associated risks. Additionally, monitor your systems for any unusual activity that may indicate a breach.
Conclusion
The jsonify-settings package has been compromised with malicious code, posing a serious threat to users. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring and using tools like Vulert can help in identifying vulnerabilities in your applications.
See every vulnerability recorded for jsonify-settings →
FAQ
You should immediately remove the package and rotate any secrets or keys stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
Currently, there is no patched version available. The best course of action is to remove the package entirely.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential system compromise.
While many npm packages are safe, it is essential to monitor and audit your dependencies regularly to mitigate risks.
