Malicious Code Injection in bella-kepok98-ruro Package

bella-kepok98-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99894: Malicious code in bella-kepok98-ruro (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The bella-kepok98-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious code that modifies package metadata and repackages itself under random names.

Vulnerability Detail

The vulnerability in the bella-kepok98-ruro package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to continuously republish itself with randomized names, polluting the npm registry and potentially leading to security risks for developers who inadvertently use these compromised packages. The origin of this vulnerability is linked to the broader tea.xyz token reward scheme, which has been identified as a source of numerous malicious packages flooding the npm ecosystem.

How To Fix

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

npm uninstall bella-kepok98-ruro

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 bella-kepok98-ruro package and any packages that depend on it. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The bella-kepok98-ruro package has been identified as containing malicious code that poses a risk to developers using npm. It is crucial to remove this package from your projects and monitor for any similar vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for bella-kepok98-ruro →

Share this vulnerability

FAQ

The bella-kepok98-ruro package is an npm package involved in a token reward campaign, designed to generate and publish derivative packages automatically.

The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry with compromised packages.

If you have installed the bella-kepok98-ruro package, you should uninstall it immediately using the command: npm uninstall bella-kepok98-ruro.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Yes, consider using alternative packages that provide similar functionality but are known to be secure and free from malicious code.

How To Fix

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

npm uninstall bella-kepok98-ruro

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