Critical Malicious Code Vulnerability in kambxjowhdsgyw Package

kambxjowhdsgyw Updated 23 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16397: Malicious code in kambxjowhdsgyw (npm). Affects kambxjowhdsgyw versions 1.0.0 – 1.0.2. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The kambxjowhdsgyw package is a Node.js library available through npm, designed for various functionalities in JavaScript applications. However, it has been identified to contain malicious code that poses significant security risks to systems utilizing it. This vulnerability can lead to unauthorized access and control over affected systems.

Vulnerability Detail

The kambxjowhdsgyw package has been found to contain malicious code that can compromise any system where it is installed. The origin of this vulnerability stems from the package itself, which may have been intentionally crafted to include harmful scripts. The ramifications of this vulnerability are severe, as it can lead to data breaches, unauthorized access to sensitive information, and potential control over the affected systems. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall kambxjowhdsgyw

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 any functionalities that rely on the kambxjowhdsgyw package until it is removed or updated. Additionally, ensure that all secrets and keys stored on the affected system are rotated immediately from a secure location.

Conclusion

The kambxjowhdsgyw package contains malicious code that poses serious security risks. It is essential to remove this package from your systems and take necessary precautions to secure your data. Regular monitoring of your dependencies can help prevent similar vulnerabilities in the future.

See every vulnerability recorded for kambxjowhdsgyw →

Share this vulnerability

FAQ

The kambxjowhdsgyw package is a Node.js library available on npm, used for various functionalities in JavaScript applications.

If you have the kambxjowhdsgyw package installed, your system is considered compromised. Use tools like Vulert to monitor and check for vulnerabilities.

Immediately remove the kambxjowhdsgyw package and rotate any secrets or keys stored on the affected system.

Regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall kambxjowhdsgyw

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