Malicious Code Injection in zul-semur46-breki: A Threat to npm Users

zul-semur46-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-76643: Malicious code in zul-semur46-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 'zul-semur46-breki' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, ultimately aiming to inflate developer reputation scores for token rewards. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in 'zul-semur46-breki' originates from its association with a malicious campaign that includes scripts designed to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include potential pollution of the npm registry, unauthorized access to sensitive information, and a compromised development environment, which can affect the integrity of applications relying on these packages.

How To Fix

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

npm uninstall zul-semur46-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 'zul-semur46-breki' package and any other packages associated with the tea.xyz token reward campaign. Monitor your package dependencies closely and consider using tools like Vulert to identify vulnerabilities in your project. You can check for affected packages using the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The 'zul-semur46-breki' package poses a significant threat to npm users due to its malicious nature and the potential for widespread impact on the npm registry. It is essential to take immediate action by removing the package and monitoring your dependencies to ensure the security of your applications.

See every vulnerability recorded for zul-semur46-breki →

Share this vulnerability

FAQ

It is a malicious npm package associated with a token reward campaign that modifies package.json files to inflate developer reputation scores.

The vulnerability can lead to unauthorized modifications in your project's dependencies, potentially compromising the integrity and security of your application.

You should uninstall the package immediately using 'npm uninstall zul-semur46-breki' and audit your project for other potentially malicious packages.

Regularly update your dependencies, use trusted sources for packages, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check your application 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 zul-semur46-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