Malicious Code Injection in yuda-6 Package: A Threat to npm Users

yuda-6 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170598: Malicious code in yuda-6 (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 yuda-6 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores for rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the yuda-6 package originates from its association with a campaign that floods the npm registry with malicious packages. The malicious payload 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 variants, which pollutes the npm registry and can potentially harm developers and users relying on legitimate packages.

How To Fix

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

npm uninstall yuda-6

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 yuda-6 package and monitor your project for any dependencies that may rely on it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The yuda-6 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for yuda-6 →

Share this vulnerability

FAQ

The yuda-6 package is part of a campaign that generates and publishes derivative npm packages to inflate developer reputation scores.

The malicious code modifies your package.json file and can lead to the pollution of the npm registry, potentially affecting the integrity of your project.

You should remove the yuda-6 package from your project and monitor for any updates or patches that may address this vulnerability.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just your package-lock.json file.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about vulnerabilities in the packages you use.

How To Fix

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

npm uninstall yuda-6

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