Critical Malicious Code Vulnerability in kyxhiagent Package

kyxhiagent Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1953: Malicious code in kyxhiagent (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 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

The kyxhiagent package is an npm module that is used for various functionalities in JavaScript applications. However, it has been identified as containing malicious code, which poses a significant security risk to any system where it is installed. This vulnerability allows attackers to gain full control over the affected systems, compromising sensitive data and secrets.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the kyxhiagent package. Any system running this package is considered fully compromised, with potential ramifications including unauthorized access to sensitive information, data breaches, and the installation of additional malicious software. The malicious code can execute arbitrary commands, leading to complete control over the affected system.

How To Fix

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

npm uninstall kyxhiagent

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

There are no effective workarounds for this vulnerability. The only recommended action is to remove the kyxhiagent package entirely from your system.

Conclusion

The kyxhiagent package poses a severe security risk due to embedded malicious code. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring for vulnerabilities using tools like Vulert is recommended to prevent future incidents.

See every vulnerability recorded for kyxhiagent →

Share this vulnerability

FAQ

You should uninstall the kyxhiagent package immediately and rotate any secrets or keys stored on your system.

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

Failure to remove kyxhiagent can lead to unauthorized access to your system, data breaches, and potential further exploitation by attackers.

After removing the package, it is essential to rotate all sensitive information and keys. Ensure that your system is scanned for any additional malicious software.

Yes, you can continue using your application, but ensure that you replace any functionality that relied on kyxhiagent with a secure alternative.

How To Fix

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

npm uninstall kyxhiagent

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