Malicious Code Injection in uyafru-tut-dutut Package: A Threat to npm Users

uyafru-tut-dutut Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170194: Malicious code in uyafru-tut-dutut (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 uyafru-tut-dutut package is part of a broader campaign targeting npm users, leveraging the tea.xyz token reward system. This package, like many others involved in the campaign, is designed to manipulate the npm ecosystem by automatically generating and publishing derivative packages. Its primary function is to inflate developer reputation scores through the creation of numerous randomized package names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The uyafru-tut-dutut package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is part of a larger scheme to automate the publication of these packages, thereby compromising the integrity of the npm registry and potentially affecting developers who rely on these packages for their projects. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with such malicious packages.

How To Fix

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

npm uninstall uyafru-tut-dutut

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 uyafru-tut-dutut package and any other packages associated with 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 requiring any signup.

Conclusion

The uyafru-tut-dutut package poses a significant threat to npm users due to its malicious code that alters package metadata and floods the npm registry with derivative packages. 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 uyafru-tut-dutut →

Share this vulnerability

FAQ

The uyafru-tut-dutut package is an npm package involved in a malicious campaign to inflate developer reputation scores through automated package publishing.

The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your project and affecting its integrity.

You should remove the uyafru-tut-dutut package from your project and monitor for any updates or patches that may be released.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

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 uyafru-tut-dutut

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