Critical Malicious Code Vulnerability in mui-path-imports Package

mui-path-imports Updated 13 Mar 2026

Summary

11/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1332: Malicious code in mui-path-imports (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mui-path-imports package is an npm library designed to facilitate the importation of Material-UI components in JavaScript applications. It is widely used for its ease of integration and ability to streamline the development process. However, this package has been found to contain malicious code that poses significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the mui-path-imports package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. Once installed, the package grants full control of the affected computer to external entities, making it imperative for users to act swiftly to mitigate potential damage.

How To Fix

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

npm uninstall mui-path-imports

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

Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package entirely and securing the system.

Conclusion

The mui-path-imports package contains a critical vulnerability due to embedded malicious code, posing severe risks to any system where it is installed. Immediate action is required to uninstall the package and secure sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their dependencies.

See every vulnerability recorded for mui-path-imports →

Share this vulnerability

FAQ

You should uninstall the mui-path-imports package immediately and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Leaving the mui-path-imports package installed can lead to unauthorized access to your system, potentially compromising sensitive data and allowing malicious actors to control your computer.

The best recovery method is to uninstall the package and rotate all secrets and keys. However, there is no guarantee that all malicious software will be removed simply by uninstalling the package.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

How To Fix

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

npm uninstall mui-path-imports

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