Malicious Code Injection in rina-keraktelor11-riris: A Threat to npm Ecosystem

rina-keraktelor11-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90162: Malicious code in rina-keraktelor11-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package rina-keraktelor11-riris 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 lies in its ability to modify critical files and republish itself under random names, thereby affecting the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the package's involvement in a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with altered names and versions. This behavior not only inflates developer reputation scores but also modifies the package.json file to remove private flags, potentially exposing sensitive information. The continuous republishing of these variants pollutes the npm registry, making it difficult for developers to trust the integrity of packages.

How To Fix

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

npm uninstall rina-keraktelor11-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 measure, you can avoid using the rina-keraktelor11-riris package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities without needing to access the code directly.

Conclusion

The rina-keraktelor11-riris package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing itself. It is essential for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications.

See every vulnerability recorded for rina-keraktelor11-riris →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the exposure of sensitive information and the pollution of the npm registry, making it difficult to trust other packages.

You should uninstall the package immediately and monitor your project for any further vulnerabilities.

You can use tools like Vulert, which allows you to monitor your package-lock.json for vulnerabilities in real-time without needing to access the code.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall rina-keraktelor11-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