Malicious Code Injection in bella-rendang65-ruro Package

bella-rendang65-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99920: Malicious code in bella-rendang65-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 bella-rendang65-ruro package is part of the npm ecosystem, often utilized in JavaScript applications. This package has been identified as part of a broader malicious campaign targeting npm, where packages are created to inflate developer reputation scores through automated publishing scripts. The vulnerability stems from the package's design, which allows it to modify critical files and republish itself with altered metadata.

Vulnerability Detail

The vulnerability in the bella-rendang65-ruro package originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these packages, leading to potential security breaches and reputation damage.

How To Fix

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

npm uninstall bella-rendang65-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 measure, you can avoid using the bella-rendang65-ruro package and replace it with a trusted alternative. If you need to maintain functionality, consider using a local version of the package that does not include the malicious scripts.

Conclusion

The bella-rendang65-ruro package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package from their projects and to stay vigilant about the packages they use. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for bella-rendang65-ruro →

Share this vulnerability

FAQ

The bella-rendang65-ruro package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to unauthorized modifications of your project's package.json file, potentially compromising your application's integrity and security.

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

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, consider using well-known and trusted packages that provide similar functionality without the associated risks.

How To Fix

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

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