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

yuda-18 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170585: Malicious code in yuda-18 (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

yuda-18 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 has been known to flood the npm ecosystem with harmful packages. The primary function of yuda-18 is to serve as a tool for developers, but its compromised nature poses significant risks to users and their projects.

Vulnerability Detail

The vulnerability in yuda-18 originates from its design to include malicious scripts that manipulate package.json files. These scripts remove private flags, alter version numbers, and create random package names to inflate developer reputation scores for token rewards. The continuous republishing of these variants leads to pollution of the npm registry, potentially compromising the integrity of other packages and projects relying on npm.

How To Fix

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

npm uninstall yuda-18

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, consider removing the yuda-18 package from your project and replacing it with a trusted alternative. You can do this by executing: 'npm uninstall yuda-18'. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The yuda-18 package poses a significant threat due to its malicious code designed to manipulate npm registry entries. It is essential for developers to be vigilant, regularly update their packages, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard your projects from such threats.

See every vulnerability recorded for yuda-18 →

Share this vulnerability

FAQ

yuda-18 is an npm package that has been linked to a malicious campaign aimed at manipulating developer reputation scores through the npm registry.

The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your project's dependencies and security.

If you have yuda-18 installed, you should uninstall it immediately and check for any unauthorized changes in your project files.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json. You can check your application for vulnerabilities without signing up at the Vulert playground.

To prevent similar vulnerabilities, regularly update your packages, monitor your dependencies, and use tools like Vulert to stay informed about potential threats.

How To Fix

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

npm uninstall yuda-18

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