Malicious Code Injection in Vina-dodol10-breki Package

vina-dodol10-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-76053: Malicious code in vina-dodol10-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

Vina-dodol10-breki is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants that can clutter the npm ecosystem.

Vulnerability Detail

The vulnerability in the vina-dodol10-breki package stems from its inclusion in a broader malicious campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages. The payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to confusion and potential security risks for users.

How To Fix

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

npm uninstall vina-dodol10-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, avoid using the vina-dodol10-breki package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure they are secure.

Conclusion

The vina-dodol10-breki package has been identified as a malicious entity within the npm ecosystem, capable of compromising project integrity through automated scripts. Immediate action is required to remove this package and safeguard your project from potential risks. Utilizing tools like Vulert can enhance your ability to monitor and manage open-source vulnerabilities effectively.

See every vulnerability recorded for vina-dodol10-breki →

Share this vulnerability

FAQ

Vina-dodol10-breki is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic publication of derivative packages.

The vulnerability can lead to the installation of malicious code that modifies your project's package.json file and can clutter the npm registry, potentially affecting your project's integrity.

You should uninstall the vina-dodol10-breki package immediately using the command npm uninstall vina-dodol10-breki and check for any other affected packages.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check for vulnerabilities without signing up at the Vulert playground.

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

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 vina-dodol10-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