Critical Malicious Code Vulnerability in klywarn Package

klywarn Updated 07 Jan 2026

Summary

07/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-118: Malicious code in klywarn (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 klywarn package is an npm library designed for various functionalities within JavaScript applications. It is commonly used for managing alerts and notifications in web applications. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations using it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the klywarn package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to data breaches and unauthorized control over affected systems. Users are advised to treat any system with this package as compromised and take immediate action.

How To Fix

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

npm uninstall klywarn

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 other than removing the klywarn package entirely. Users should ensure that their systems are secure and monitor for any signs of compromise.

Conclusion

The klywarn package has been identified as containing malicious code that poses a serious threat to any system it is installed on. Immediate removal of the package and rotation of sensitive information is essential to mitigate the risks associated with this vulnerability. Users should remain vigilant and utilize tools like Vulert to monitor for potential vulnerabilities in their applications.

See every vulnerability recorded for klywarn →

Share this vulnerability

FAQ

You should immediately uninstall the klywarn package and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Keeping klywarn installed poses significant risks, including unauthorized access to sensitive data and complete control over your system by malicious actors.

After removing the package, ensure that all secrets and keys are rotated. It is also advisable to conduct a thorough security audit of your system.

Yes, you can report this vulnerability to the appropriate security channels or platforms that track open-source vulnerabilities.

How To Fix

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

npm uninstall klywarn

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