Malicious Code Injection in @mntv-analysis/workspaces-components Package
Summary
MAL-2026-17871: Malicious code in @mntv-analysis/workspaces-components (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 @mntv-analysis/workspaces-components package is an npm library that is intended to provide various workspace components for developers. However, it has been compromised through a dependency confusion attack, where a malicious version of the package was published to exploit misconfigured package resolvers. This vulnerability allows attackers to execute harmful code on user systems during installation.
Vulnerability Detail
The vulnerability originates from a malicious package published by the npm user 'conx3993'. This package squats on a name similar to an internal package and uses a version number that causes it to be selected over the legitimate package. Upon installation, a 'preinstall' hook executes a script that sends a GET request to an attacker-controlled server with the victim's public IP address and a unique authorization token. This not only exposes the victim's IP address but also informs the attacker which internal package was installed, leading to potential further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @mntv-analysis/workspaces-componentsIf 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 @mntv-analysis/workspaces-components package until the issue is resolved. Additionally, you can configure your package manager to only resolve packages from trusted sources or internal registries to prevent such dependency confusion attacks.
Conclusion
The @mntv-analysis/workspaces-components package has been compromised through a dependency confusion attack, leading to the execution of malicious code on user systems. It is essential to remove the affected package and replace it with a legitimate version to safeguard your application. Regular monitoring and auditing of dependencies are crucial to maintaining security.
See every vulnerability recorded for @mntv-analysis/workspaces-components →
FAQ
Dependency confusion is a type of attack where a malicious package is published to a public repository with the same name as an internal package, tricking package managers into installing the malicious version.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can identify if your application is affected by this vulnerability.
If you have installed the malicious package, immediately remove it from your project and replace it with the legitimate version. Review your code for any potential security breaches.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and configure your package manager to prioritize internal packages.
Yes, using tools like Vulert, you can automate the detection of open-source vulnerabilities without needing to access the code or installation. You can check your application using the Vulert playground.
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.
