Malicious Code Injection in udin-buburayam87-breki Package

udin-buburayam87-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75804: Malicious code in udin-buburayam87-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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The udin-buburayam87-breki package is part of the npm ecosystem and is 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 compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious scripts that modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This behavior can result in security risks for developers who unknowingly use these compromised packages, potentially leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall udin-buburayam87-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 workaround, you can avoid using the udin-buburayam87-breki package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The udin-buburayam87-breki package poses significant security risks due to its malicious code that alters package configurations and republish variants. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for udin-buburayam87-breki →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign and is known to contain malicious code.

The malicious code can modify your package.json file, remove private flags, and publish unauthorized packages, leading to potential security risks.

You should uninstall the package immediately using 'npm uninstall udin-buburayam87-breki' and check your project for any unauthorized changes.

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 your application for vulnerabilities using the Vulert playground at Vulert Scanner.

Yes, you should look for other npm packages that provide similar functionality without the associated risks of malicious code.

How To Fix

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

npm uninstall udin-buburayam87-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