Malicious Code Injection in yuda-15: A Threat to npm Ecosystem

yuda-15 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170582: Malicious code in yuda-15 (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 yuda-15 is part of the npm ecosystem and has been implicated in a malicious campaign that aims to exploit the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with numerous derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in yuda-15 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 these variants, which pollutes the npm registry and can mislead developers into using compromised packages. 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 yuda-15

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 workaround, you can manually check your package-lock.json file for any references to yuda-15 and remove them. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The yuda-15 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repopulates the registry with compromised variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for yuda-15 →

Share this vulnerability

FAQ

Yuda-15 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

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

You should remove the yuda-15 package from your project immediately to mitigate any risks associated with its malicious behavior.

It is advisable to exercise caution and thoroughly review the source and functionality of any package before installation, especially those associated with known malicious campaigns.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time, helping you stay informed about potential risks.

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 yuda-15

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