Malicious Code Injection in bambang-kue78-ruro Package

bambang-kue78-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99767: Malicious code in bambang-kue78-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The bambang-kue78-ruro package is part of the npm ecosystem, primarily used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that manipulate developer reputation scores. This package, like others in the campaign, is designed to generate and publish derivative packages with randomized names, potentially compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting developers who rely on these packages for legitimate purposes. The malicious payload can also inflate developer reputation scores fraudulently, undermining trust in the npm ecosystem.

How To Fix

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

npm uninstall bambang-kue78-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, avoid using the bambang-kue78-ruro package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure no malicious packages are included.

Conclusion

The bambang-kue78-ruro package poses a significant risk due to its malicious code designed to manipulate npm registry integrity. It is crucial for developers to remove this package and monitor their dependencies to maintain a secure development environment.

See every vulnerability recorded for bambang-kue78-ruro →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for generating and publishing derivative packages.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You should uninstall the package immediately and audit your dependencies for any other malicious packages.

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

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall bambang-kue78-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