Malicious Code Injection in vida-kue37-breki: A Threat to npm Ecosystem

vida-kue37-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-76021: Malicious code in vida-kue37-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package vida-kue37-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability in vida-kue37-breki stems from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.

How To Fix

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

npm uninstall vida-kue37-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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that you do not include vida-kue37-breki in your package.json file.

Conclusion

The vida-kue37-breki package poses a significant risk to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and take immediate action to remove such packages from their projects. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for vida-kue37-breki →

Share this vulnerability

FAQ

vida-kue37-breki is an npm package that has been identified as malicious, associated with the tea.xyz token reward campaign.

This vulnerability can compromise the integrity of your project by polluting the npm registry and potentially affecting your application's reputation.

If you have installed vida-kue37-breki, you should uninstall it immediately using 'npm uninstall vida-kue37-breki'.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Check your application against known vulnerabilities using the Vulert playground.

To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and avoid installing unverified packages.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall vida-kue37-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