Malicious Code Vulnerability in @inpeek/odata-angular: Dependency Confusion Attack
Summary
MAL-2026-17543: Malicious code in @inpeek/odata-angular (npm). Affects @inpeek/odata-angular versions 99.99.100 – 99.99.99. 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 @inpeek/odata-angular package is a JavaScript library available on the npm registry, primarily used for integrating OData services with Angular applications. It is designed to facilitate data retrieval and manipulation in a structured manner. However, this package has been compromised, leading to a significant security vulnerability that exposes users to potential data leaks.
Vulnerability Detail
The vulnerability stems from a dependency-confusion attack where the malicious version of @inpeek/odata-angular (99.99.102) was published to the public npm registry. This version is designed to override an internal package of the same name, causing any installation to execute a post-install script that sends sensitive host information to an attacker-controlled server. The script, located in ping.js, collects data such as the operating system hostname, platform, and Node.js version, which can be exploited by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @inpeek/odata-angularIf 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 @inpeek/odata-angular package from the public npm registry. Instead, use the internal version of the package or consider alternative libraries that provide similar functionality without the associated risks.
Conclusion
The @inpeek/odata-angular package has been compromised through a dependency-confusion attack, leading to the potential leakage of sensitive information. It is essential for developers to take immediate action by updating to a secure version and employing tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for @inpeek/odata-angular →
FAQ
A dependency-confusion attack occurs when a malicious package is published to a public registry with the same name as an internal package, tricking the package manager into installing the malicious version.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected by this vulnerability.
The malicious package collects sensitive information such as the operating system hostname, platform, and Node.js version, which can be sent to an external server controlled by attackers.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid installing packages from untrusted sources.
If you have installed the malicious version, immediately uninstall it and update to a secure version. Additionally, review your system for any unauthorized access or data breaches.
