Malicious Code Injection in vida-soto15-breki: A Threat to npm Packages

vida-soto15-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-76044: Malicious code in vida-soto15-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 vida-soto15-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, notorious for flooding the npm registry with malicious packages. Its primary function is to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, this functionality comes with significant risks, as it can lead to the proliferation of malicious code within the npm ecosystem.

Vulnerability Detail

The vulnerability in vida-soto15-breki stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants of the package, polluting the npm registry and potentially compromising other projects that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the malicious activities.

How To Fix

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

npm uninstall vida-soto15-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 the affected package by using npm's package-lock.json file to lock dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json to alert you of any open-source vulnerabilities in real-time.

Conclusion

The vida-soto15-breki package poses a significant risk due to its malicious code injection capabilities. It is essential to stay informed about such vulnerabilities and take proactive measures to protect your projects. Regularly updating packages and utilizing tools like Vulert can help maintain the integrity of your software.

See every vulnerability recorded for vida-soto15-breki →

Share this vulnerability

FAQ

vida-soto15-breki is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability can lead to the modification of your package.json file, removal of private flags, and the introduction of malicious code, potentially compromising your project.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If no patched version is available, it is recommended to remove the affected package from your project to mitigate risks.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

How To Fix

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

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