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

yuda-16 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170583: Malicious code in yuda-16 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package yuda-16 is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is intended for developers looking to enhance their reputation through token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability in yuda-16 originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the automatic generation and publication of derivative packages, polluting the npm registry and potentially harming developers' reputations. The malicious payload is designed to inflate developer scores fraudulently, making it a significant threat to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall yuda-16

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 remove the yuda-16 package from your project by executing the following command: npm uninstall yuda-16. This will prevent any malicious activity associated with the package until a fix is implemented.

Conclusion

The yuda-16 package poses a significant risk due to its malicious code that alters project files and affects the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for yuda-16 →

Share this vulnerability

FAQ

yuda-16 is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to reputation damage and registry pollution.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities. You can check your application using the Vulert playground at Vulert Scanner without any signup.

If no patched version is available, it is advisable to uninstall the yuda-16 package from your project to mitigate risks.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall yuda-16

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