Malicious Code Injection in uyafu-tutadat-datut Package: A Threat to npm Ecosystem

uyafu-tutadat-datut Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170200: Malicious code in uyafu-tutadat-datut (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 uyafu-tutadat-datut package is part of a broader initiative related to the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to alter critical files and continuously pollute the npm registry.

Vulnerability Detail

The vulnerability in the uyafu-tutadat-datut package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to a significant risk of registry pollution. The malicious payload can compromise the integrity of the npm ecosystem, affecting developers who rely on these packages for legitimate purposes.

How To Fix

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

npm uninstall uyafu-tutadat-datut

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 measure, you can avoid using the uyafu-tutadat-datut package and any other packages that may be part of the tea.xyz token reward campaign. 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 uyafu-tutadat-datut package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and utilize tools like Vulert to ensure their projects remain secure from such vulnerabilities.

See every vulnerability recorded for uyafu-tutadat-datut →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to manipulate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of packages and potentially affecting your project's dependencies.

You should remove the uyafu-tutadat-datut package from your project and monitor for any updates or patches.

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

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with security advisories.

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 uyafu-tutadat-datut

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