Malicious Code Injection in @mntv-analysis/ui Package - Dependency Confusion Vulnerability

@mntv-analysis/ui Updated 14 Oct 2026

Summary

13/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17869: Malicious code in @mntv-analysis/ui (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @mntv-analysis/ui package is an npm library that is intended to provide user interface components for web applications. However, it has been compromised through a dependency confusion attack, where a malicious actor published a package that mimics the name of an internal package. This vulnerability allows the attacker to execute arbitrary code during the installation process, posing significant risks to users who inadvertently install it.

Vulnerability Detail

The vulnerability originates from a malicious npm user who published a package named @mntv-analysis/ui with a version number that is likely to be picked over the legitimate package due to misconfigured package resolvers. The malicious version (99.1.1) contains a preinstall hook that executes a script (index.js) which sends the victim's public IP address to an attacker-controlled server (realwbx.com) along with a hard-coded authorization token. This action not only exposes the victim's IP address but also informs the attacker about the internal package that was installed, potentially leading to further exploitation.

How To Fix

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

npm uninstall @mntv-analysis/ui

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 @mntv-analysis/ui package until a secure version is released. Additionally, consider using a package manager that supports lock files and can help prevent dependency confusion attacks.

Conclusion

The @mntv-analysis/ui package has been compromised through a dependency confusion attack, allowing malicious code to be executed during installation. Users are advised to uninstall the package immediately and monitor their applications for any signs of exploitation. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for @mntv-analysis/ui →

Share this vulnerability

FAQ

Dependency confusion occurs when a malicious package is published with the same name as an internal package, tricking package managers into installing the malicious version instead of the legitimate one.

You can use Vulert, which monitors and alerts 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.

Immediately uninstall the @mntv-analysis/ui package using the command: npm uninstall @mntv-analysis/ui. Review your codebase for any potential impacts from the malicious code.

Always verify the source and integrity of packages before installation. Use tools like Vulert to monitor your dependencies for vulnerabilities in real-time.

Yes, you can report malicious packages to the npm security team or through platforms like GitHub where the package is hosted.

How To Fix

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

npm uninstall @mntv-analysis/ui

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