Malicious Code Injection in bella-lapis30-ruro Package - npm Vulnerability

bella-lapis30-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99899: Malicious code in bella-lapis30-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 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 bella-lapis30-ruro package is part of the npm ecosystem, typically used for various JavaScript applications. It has gained notoriety due to its involvement in the tea.xyz token reward campaign, which has led to the proliferation of malicious packages designed to inflate developer reputation scores. This package specifically contains scripts that automate the generation and publication of derivative packages, making it susceptible to exploitation.

Vulnerability Detail

The vulnerability in the bella-lapis30-ruro package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry by continuously republishing variants, which can lead to reputational damage for developers and potential security risks for applications relying on this package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been identified as a source of numerous malicious npm packages.

How To Fix

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

npm uninstall bella-lapis30-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 remove the bella-lapis30-ruro package from your project by executing the following command: npm uninstall bella-lapis30-ruro. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The bella-lapis30-ruro package has been identified as containing malicious code that poses a significant risk to applications using it. It is imperative for developers to take immediate action by updating or removing the package to safeguard their projects from potential exploitation.

See every vulnerability recorded for bella-lapis30-ruro →

Share this vulnerability

FAQ

The bella-lapis30-ruro package is an npm package that has been associated with malicious activities, specifically designed to inflate developer reputation scores through the tea.xyz token reward campaign.

The vulnerability can lead to the modification of your package.json file, removal of private flags, and the generation of random package names, which can compromise the integrity of your application and pollute the npm registry.

If you are using the bella-lapis30-ruro package, it is crucial to update it to a patched version or remove it entirely from your project to mitigate the risks associated with this vulnerability.

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 without any signup.

Detailed information about this vulnerability can be found in the Open Source Vulnerability database and through security advisories related to the npm ecosystem.

How To Fix

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

npm uninstall bella-lapis30-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