Critical Malicious Code Vulnerability in initial-path Package
Summary
MAL-2025-191463: Malicious code in initial-path (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 initial-path package is a Node.js library commonly used in npm ecosystems to manage file paths in applications. It provides developers with utilities to handle path operations efficiently. However, this package has been identified as containing malicious code, posing significant security risks to systems that utilize it.
Vulnerability Detail
The vulnerability originates from the inclusion of embedded malicious code within the initial-path package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be harmful in nature. Users should be aware that simply removing the package may not eliminate all traces of the malicious software, as full control of the affected computer may have been granted to an external entity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall initial-pathIf 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
Currently, there are no specific workarounds to mitigate the risks posed by this vulnerability other than removing the package and securing your system.
Conclusion
The initial-path package has been identified as containing malicious code, posing serious security risks to systems that utilize it. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor their dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for initial-path →
FAQ
You should immediately remove the initial-path package and rotate any sensitive information stored on your system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Failing to address this vulnerability could lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
Yes, Vulert provides a service that monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.
It is advisable to avoid using the initial-path package until a verified and secure version is released.
