Malicious Code Injection in xaver-klentik13-riris Package

xaver-klentik13-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-92364: Malicious code in xaver-klentik13-riris (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 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 xaver-klentik13-riris 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 npm's publishing system. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward program.

Vulnerability Detail

The vulnerability in the xaver-klentik13-riris 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 then continuously republished to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion attacks and the proliferation of untrusted packages in the ecosystem.

How To Fix

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

npm uninstall xaver-klentik13-riris

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-klentik13-riris package and instead look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The xaver-klentik13-riris package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with untrusted packages. It is crucial to remove this package from your projects and monitor for any similar vulnerabilities.

See every vulnerability recorded for xaver-klentik13-riris →

Share this vulnerability

FAQ

The xaver-klentik13-riris package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code modifies your package.json file, which can lead to the introduction of untrusted dependencies and potential security vulnerabilities.

You should uninstall the xaver-klentik13-riris package immediately using 'npm uninstall xaver-klentik13-riris' to mitigate any risks.

Yes, you can search for alternative npm packages that provide similar functionality without the associated risks of malicious code.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall xaver-klentik13-riris

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