Malicious Code Injection in rudi-dodol71-breki: A Threat to npm Ecosystem

rudi-dodol71-breki Updated 23 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75309: Malicious code in rudi-dodol71-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 rudi-dodol71-breki is part of a larger set of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses significant risks to developers who may unknowingly use these packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the rudi-dodol71-breki package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The continuous republishing of these variants can mislead developers and potentially introduce security risks into their applications. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards.

How To Fix

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

npm uninstall rudi-dodol71-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 avoid using the rudi-dodol71-breki package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential risks.

Conclusion

The rudi-dodol71-breki package represents a significant threat to the npm ecosystem due to its malicious behavior aimed at exploiting developer reputation systems. 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 rudi-dodol71-breki →

Share this vulnerability

FAQ

rudi-dodol71-breki is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should immediately uninstall the rudi-dodol71-breki package and audit your project for any other potentially malicious dependencies.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

There is no patch for the rudi-dodol71-breki package since it is a malicious package. The best course of action is to remove it from your project.

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 rudi-dodol71-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