Malicious Code Injection in indah-ubi20-breki: A Threat to npm Users

indah-ubi20-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73509: Malicious code in indah-ubi20-breki (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 package 'indah-ubi20-breki' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automatically generate and publish derivative versions with randomized names, aiming to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, thus polluting the npm registry.

Vulnerability Detail

The vulnerability in 'indah-ubi20-breki' stems from its malicious code that alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the package but also poses a risk of flooding the npm registry with unwanted variants, potentially affecting other developers and users relying on npm for package management.

How To Fix

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

npm uninstall indah-ubi20-breki

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 'indah-ubi20-breki' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The 'indah-ubi20-breki' package poses a significant risk due to its malicious code that alters critical files and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for similar vulnerabilities using tools like Vulert to maintain the integrity of their applications.

See every vulnerability recorded for indah-ubi20-breki →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json and floods the npm registry with unwanted variants.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you have installed the package, you should uninstall it immediately using 'npm uninstall indah-ubi20-breki'.

Yes, you should look for alternative packages that offer similar functionality but do not have the associated risks of malicious code.

Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential threats.

How To Fix

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

npm uninstall indah-ubi20-breki

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