Malicious Code Injection in bayu-ruwet96-ruro Package: A Threat to npm Users

bayu-ruwet96-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99852: Malicious code in bayu-ruwet96-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The bayu-ruwet96-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, its malicious nature poses significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the bayu-ruwet96-ruro package stems from its inclusion in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior not only compromises the security of the affected applications but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can lead to unauthorized access and manipulation of user data.

How To Fix

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

npm uninstall bayu-ruwet96-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 the bayu-ruwet96-ruro package by using npm's package-lock.json file to lock your dependencies to known safe versions. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The bayu-ruwet96-ruro package poses a significant threat to npm users due to its malicious code that modifies package files and publishes harmful variants. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for bayu-ruwet96-ruro →

Share this vulnerability

FAQ

The bayu-ruwet96-ruro package is an npm package involved in a token reward campaign that automates the generation of derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your application to security risks and affecting its integrity.

You should uninstall the bayu-ruwet96-ruro package immediately and check for any dependencies that may rely on it.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall bayu-ruwet96-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