Malicious Code Injection in indah-buburayam58-ruro Package

indah-buburayam58-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104097: Malicious code in indah-buburayam58-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 indah-buburayam58-ruro package is part of the npm ecosystem, often associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies its own package.json file and republishes variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This malicious behavior involves modifying the package.json file to remove private flags, altering version numbers, and continuously republishing variants, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.

How To Fix

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

npm uninstall indah-buburayam58-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 indah-buburayam58-ruro package in your project. Additionally, consider using package-lock.json to monitor dependencies and ensure that no malicious packages are included.

Conclusion

The indah-buburayam58-ruro package contains a significant vulnerability that can lead to malicious code injection and npm registry pollution. It is crucial to uninstall this package and monitor your dependencies for any potential threats. Utilizing tools like Vulert can help maintain the security of your project.

See every vulnerability recorded for indah-buburayam58-ruro →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish 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 using 'npm uninstall indah-buburayam58-ruro' and monitor your dependencies for any malicious activity.

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

It is advisable to keep an eye on updates from the package maintainers. If a patched version is released, update your package to ensure security.

How To Fix

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

npm uninstall indah-buburayam58-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