Critical Malicious Code Vulnerability in Extended-Path Package
Summary
MAL-2026-240: Malicious code in extended-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The extended-path package is a Node.js library designed to enhance file path manipulation capabilities within applications. It allows developers to work with file paths more efficiently, providing utilities for path resolution and normalization. However, the package has been compromised, leading to severe security risks for any system utilizing it.
Vulnerability Detail
The vulnerability originates from the presence of malicious code embedded within the extended-path package. This code can fully compromise any computer that has the package installed or running, potentially allowing unauthorized access to sensitive data, including secrets and keys. The implications of this vulnerability are severe, as it may lead to complete control of the affected system by an external entity, making it critical for users to take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall extended-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
There are no effective workarounds for this vulnerability. The best course of action is to remove the package entirely and ensure that all sensitive information is secured.
Conclusion
The extended-path package has been compromised with malicious code, posing significant security risks to any system using it. Immediate removal of the package and rotation of sensitive information is crucial to mitigate potential damage. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.
See every vulnerability recorded for extended-path →
FAQ
You should immediately remove the extended-path package and rotate any secrets or keys stored on the affected machine.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
Currently, there is no patched version available. The recommended action is to remove the package entirely.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
