Critical Malicious Code Vulnerability in ndmcmsujey Package

ndmcmsujey Updated 23 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16402: Malicious code in ndmcmsujey (npm). Affects ndmcmsujey versions 1.0.0. 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

ndmcmsujey is an npm package that serves various functionalities within JavaScript applications. It is commonly used for web development tasks, but recent findings have revealed that it contains malicious code, posing significant risks to systems that utilize it. The presence of such code can lead to unauthorized access and compromise sensitive data.

Vulnerability Detail

The ndmcmsujey package has been identified to contain malicious code, which may allow attackers to gain full control over any system where the package is installed. This vulnerability originates from the package itself or its dependencies, which have been compromised. Systems running this package should be considered fully compromised, and all secrets and keys stored on those systems should be rotated immediately. The malicious code can lead to data breaches and unauthorized access to sensitive information.

How To Fix

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

npm uninstall ndmcmsujey

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 should immediately stop using the ndmcmsujey package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, ensure that you rotate any sensitive credentials that may have been exposed.

Conclusion

The ndmcmsujey package has been identified as containing malicious code, posing serious risks to any systems using it. Immediate action is required to remove the package and secure any exposed credentials. Regular monitoring of dependencies is crucial to maintain security in your applications.

See every vulnerability recorded for ndmcmsujey →

Share this vulnerability

FAQ

You should remove the ndmcmsujey package from your project immediately and rotate any sensitive credentials.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

Currently, there is no patch available for the ndmcmsujey package. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation of sensitive information.

While many npm packages are safe, it is essential to regularly monitor and audit your dependencies for vulnerabilities. Tools like Vulert can help with this.

How To Fix

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

npm uninstall ndmcmsujey

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