Critical Malicious Code Vulnerability in multi-provider-settings Package
Summary
MAL-2025-190553: Malicious code in multi-provider-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 multi-provider-settings package is an npm library designed to facilitate the management of multiple provider configurations in applications. It is commonly used in projects that require integration with various external services. However, this package has been compromised, leading to significant security concerns for any application utilizing it.
Vulnerability Detail
The vulnerability originates from the presence of malicious code within the multi-provider-settings package. This code can fully compromise any computer on which the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code has been confirmed by security researchers, and it poses a severe risk to the integrity and confidentiality of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall multi-provider-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 temporary measure, you can isolate the affected application from the network to prevent further exploitation while you work on removing the package and securing your environment.
Conclusion
The multi-provider-settings package has been identified as containing malicious code that poses a significant security threat. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in the future.
See every vulnerability recorded for multi-provider-settings →
FAQ
You should remove the package immediately and rotate any secrets or keys stored on the affected machine.
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, potential data breaches, and complete compromise of the affected system.
It is recommended to find an alternative package that offers similar functionality without the security risks associated with multi-provider-settings.
