Malicious Code Vulnerability in kmnb Package

kmnb Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1767: Malicious code in kmnb (npm). Affects kmnb 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 kmnb package is a JavaScript library available through the npm ecosystem, primarily used for various utility functions in Node.js applications. It is designed to simplify certain programming tasks, but like many open-source packages, it can be susceptible to vulnerabilities if not properly maintained or audited. This specific vulnerability involves the introduction of malicious code, which can compromise the integrity of applications that depend on this package.

Vulnerability Detail

The kmnb package has been identified to contain malicious code, which poses a significant risk to users. This vulnerability originated from a malicious actor who injected harmful code into the package, specifically in version 1.0.0. The ramifications of this vulnerability could include unauthorized access to sensitive data, data corruption, or even complete system compromise. Users of the kmnb package are strongly advised to take immediate action to mitigate these risks.

How To Fix

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

npm uninstall kmnb

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, users can remove the kmnb package from their project until a secure version is released. This can be done with the following command: npm uninstall kmnb. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The kmnb package has a critical vulnerability due to the presence of malicious code. Users are urged to update or remove the package to protect their applications from potential threats. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for kmnb →

Share this vulnerability

FAQ

The kmnb package is a JavaScript library used in Node.js applications for various utility functions.

The malicious code was injected by a malicious actor into the kmnb package, specifically in version 1.0.0.

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

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

If you cannot update the package, consider uninstalling it and using alternative packages until a secure version is available.

How To Fix

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

npm uninstall kmnb

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