Malicious Code Injection in bayu-tahu40-ruro Package

bayu-tahu40-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99861: Malicious code in bayu-tahu40-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-tahu40-ruro package 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 designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the bayu-tahu40-ruro package originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can compromise the security of applications relying on this package, potentially allowing unauthorized access or manipulation of data.

How To Fix

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

npm uninstall bayu-tahu40-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 bayu-tahu40-ruro package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The bayu-tahu40-ruro package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Users are advised to uninstall this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the integrity of their applications.

See every vulnerability recorded for bayu-tahu40-ruro →

Share this vulnerability

FAQ

The bayu-tahu40-ruro package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

This vulnerability can compromise the security of your application by allowing unauthorized modifications to your package metadata, potentially leading to security breaches.

If you have installed the bayu-tahu40-ruro package, you should uninstall it immediately using 'npm uninstall bayu-tahu40-ruro' and check your project for any other malicious packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Yes, the npm ecosystem has seen various malicious packages. It's crucial to stay updated on security advisories and regularly audit your dependencies.

How To Fix

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

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