Malicious Code Injection in zul-bubur20-breki Package

zul-bubur20-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-76609: Malicious code in zul-bubur20-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 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 zul-bubur20-breki package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that serve no legitimate purpose. This package, like others in its category, is designed to manipulate npm's publishing system for the benefit of its creators, compromising the integrity of the registry.

Vulnerability Detail

The vulnerability in the zul-bubur20-breki package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation of applications relying on this package.

How To Fix

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

npm uninstall zul-bubur20-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 workaround, you can avoid using the zul-bubur20-breki package altogether. If it is already included in your project, remove it by executing: npm uninstall zul-bubur20-breki. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.

Conclusion

The zul-bubur20-breki package contains malicious code that compromises the integrity of the npm registry and poses significant risks to applications relying on it. Immediate action is required to remove this package and prevent potential exploitation. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for zul-bubur20-breki →

Share this vulnerability

FAQ

The zul-bubur20-breki package is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

This vulnerability can lead to dependency confusion, where your application may unintentionally rely on malicious code, compromising its security and integrity.

You should uninstall the zul-bubur20-breki package immediately and monitor your project for any other potentially malicious packages.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall zul-bubur20-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