Malicious Code Detected in xaver-klipo89-kyuki Package - npm Vulnerability

xaver-klipo89-kyuki Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-92365: Malicious code in xaver-klipo89-kyuki (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 xaver-klipo89-kyuki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package is linked to its involvement in the tea.xyz token reward scheme, which incentivizes the creation of numerous low-quality packages to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the xaver-klipo89-kyuki package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. The primary concern is that this package continuously republishes variants, polluting the npm registry and potentially compromising the integrity of other packages. This behavior can lead to security risks for developers who unknowingly depend on these malicious packages.

How To Fix

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

npm uninstall xaver-klipo89-kyuki

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, you can avoid using the xaver-klipo89-kyuki package and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The xaver-klipo89-kyuki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to take immediate action to remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.

See every vulnerability recorded for xaver-klipo89-kyuki →

Share this vulnerability

FAQ

The xaver-klipo89-kyuki package is an npm package that has been identified as malicious, part of a campaign to flood the npm registry with low-quality packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json file and republishing variants to the npm registry.

You should uninstall the xaver-klipo89-kyuki package immediately and monitor your project for any other potentially malicious packages.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using your package-lock.json file.

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

How To Fix

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

npm uninstall xaver-klipo89-kyuki

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