Malicious Code Injection in zain-jus18-breki: A Threat to npm Ecosystem

zain-jus18-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-76504: Malicious code in zain-jus18-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package zain-jus18-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like others in the npm registry, is intended to facilitate the development and sharing of reusable code. However, it has been identified as part of a malicious campaign that exploits the npm registry by generating and publishing numerous derivative packages with altered metadata, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in zain-jus18-breki originates from its association with the tea.xyz token reward campaign. This package contains scripts designed to automatically publish derivative packages with randomized names, which can inflate developer reputation scores fraudulently. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry and potential security risks for developers using these packages.

How To Fix

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

npm uninstall zain-jus18-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 zain-jus18-breki package and monitor your project's dependencies for any similar malicious packages. Regularly audit your npm packages using the command 'npm audit' to identify vulnerabilities.

Conclusion

The zain-jus18-breki package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for zain-jus18-breki →

Share this vulnerability

FAQ

zain-jus18-breki is an npm package that has been identified as part of a malicious campaign to exploit the npm registry by publishing numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the security and integrity of your project by introducing malicious code.

If you have installed zain-jus18-breki, you should uninstall it immediately using 'npm uninstall zain-jus18-breki' and audit your project for any other vulnerabilities.

To prevent similar vulnerabilities, regularly update your dependencies, use trusted packages, and conduct audits of your npm packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check if your application is affected by visiting the Vulert playground.

How To Fix

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

npm uninstall zain-jus18-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