Critical Malicious Code Vulnerability in ndmckauxuoincv Package

ndmckauxuoincv Updated 23 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16401: Malicious code in ndmckauxuoincv (npm). Affects ndmckauxuoincv 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 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 ndmckauxuoincv package is a Node.js module available through npm, designed for various utility functions within JavaScript applications. However, it has been identified to contain malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations relying on this package for their projects.

Vulnerability Detail

The ndmckauxuoincv package has been found to contain malicious code, which can lead to full system compromise. This vulnerability originates from the package itself and has been flagged by security tools such as Amazon Inspector and GHSA. Any system running this package should be considered at risk, as it may allow unauthorized access to sensitive information, including secrets and keys stored on the affected machine.

How To Fix

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

npm uninstall ndmckauxuoincv

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 workaround, you can temporarily disable the functionality that relies on the ndmckauxuoincv package until it is removed or a secure alternative is found. Additionally, ensure that your system is monitored for any unusual activity.

Conclusion

The ndmckauxuoincv package poses a serious security threat due to the presence of malicious code. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for ndmckauxuoincv →

Share this vulnerability

FAQ

Immediately remove the package from your project and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

The risks include unauthorized access to sensitive data, potential data breaches, and complete system compromise.

Currently, there is no patched version available. It is recommended to remove the package entirely.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall ndmckauxuoincv

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