Malicious Code Vulnerability in bella-oblok1-ruro: Exploitation of npm Registry

bella-oblok1-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99909: Malicious code in bella-oblok1-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 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 package 'bella-oblok1-ruro' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automatically generate and publish derivative packages, thereby inflating developer reputation scores for token rewards. The vulnerability in this package allows for the modification of critical files, leading to potential security risks.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the package, which modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This behavior can lead to unauthorized access, reputation damage for developers, and a compromised npm ecosystem. The malicious scripts typically include autopublish functionalities that automate the creation of these harmful packages.

How To Fix

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

npm uninstall bella-oblok1-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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your package-lock.json does not include 'bella-oblok1-ruro'. You can also use the following command to remove it if it is already installed: npm uninstall bella-oblok1-ruro.

Conclusion

The 'bella-oblok1-ruro' package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial to remove this package and monitor your dependencies to maintain the integrity of your projects. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.

See every vulnerability recorded for bella-oblok1-ruro →

Share this vulnerability

FAQ

The impact includes potential unauthorized access to your project, pollution of the npm registry, and damage to your developer reputation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the package immediately using the command: npm uninstall bella-oblok1-ruro.

Currently, there are no known patches for this specific package, so the best course of action is to remove it from your project.

Regularly audit your dependencies, use tools like Vulert for monitoring, and avoid installing packages from untrusted sources.

How To Fix

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

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