Critical Malicious Code Vulnerability in set-nested-prop Package
Summary
MAL-2025-191010: Malicious code in set-nested-prop (npm). Affects set-nested-prop versions 2.0.1 – 2.0.2. 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 set-nested-prop package is an npm library designed to facilitate the manipulation of nested properties within JavaScript objects. It allows developers to easily set values at any level of a nested structure, enhancing code efficiency and readability. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any application that utilizes it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the set-nested-prop package. This code can compromise the security of any computer running the package, leading to unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code has been confirmed by security assessments from sources like Amazon Inspector and GHSA Malware, indicating that systems using this package should be considered fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall set-nested-propIf 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 avoid using the set-nested-prop package altogether and consider alternative libraries that provide similar functionality without the associated risks. Always ensure to review the security status of any package before integrating it into your project.
Conclusion
The discovery of malicious code within the set-nested-prop package poses a serious threat to any application utilizing it. Immediate action is required to mitigate risks, including uninstalling the package and rotating sensitive information. Staying vigilant and using tools like Vulert can help maintain the security of your software projects.
See every vulnerability recorded for set-nested-prop →
FAQ
Immediately uninstall the package using 'npm uninstall set-nested-prop' and rotate any secrets or keys that may have been exposed.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
While specific alternatives are not mentioned, consider using other well-reviewed npm packages that provide similar functionality without known vulnerabilities.
Failure to address this vulnerability may result in unauthorized access to sensitive data, leading to data breaches and potential legal ramifications.
Regularly check your dependencies using tools like Vulert, which provides real-time alerts for open-source vulnerabilities.
