Critical Malicious Code Vulnerability in locate-path_updated Package

locate-path_updated Updated 06 Feb 2026

Summary

05/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-752: Malicious code in locate-path_updated (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The locate-path_updated package is an npm module designed to locate the path of a specified module in a Node.js environment. It is typically used in various applications to manage dependencies and streamline module resolution. However, this package has been identified to contain malicious code, posing significant security risks to systems that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the locate-path_updated package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code has been confirmed by multiple sources, indicating that systems running this package should be considered fully compromised. The implications of this vulnerability are severe, as it can lead to data breaches and unauthorized control over affected systems.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall locate-path_updated

If 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 locate-path_updated package altogether and seek alternative packages that provide similar functionality without the associated risks. Additionally, ensure that all secrets and keys stored on the affected system are rotated from a secure environment.

Conclusion

The locate-path_updated package contains malicious code that poses a significant threat to systems using it. Immediate action is required to remove the package and secure sensitive information. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for locate-path_updated →

Share this vulnerability

FAQ

The locate-path_updated package is an npm module used to find the path of a specified module in Node.js applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

You should immediately remove the locate-path_updated package and rotate any sensitive information stored on the affected system.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure to keep your packages updated to the latest secure versions.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall locate-path_updated

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback