Malicious Code Injection in uafaru-tiut-dtut Package - npm Vulnerability

uafaru-tiut-dtut Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169464: Malicious code in uafaru-tiut-dtut (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The uafaru-tiut-dtut package is part of the npm ecosystem, often utilized for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that manipulate developer reputation scores. This package, like others in the campaign, contains scripts designed to automatically publish derivative packages with altered metadata, making it a target for malicious exploitation.

Vulnerability Detail

The vulnerability in the uafaru-tiut-dtut package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, potentially compromising the integrity of applications that depend on this package. The malicious payload is designed to continuously republish variants, which can inflate developer reputation scores fraudulently.

How To Fix

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

npm uninstall uafaru-tiut-dtut

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 prevent the installation of this package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. However, the best approach is to remove the package entirely.

Conclusion

The uafaru-tiut-dtut package poses a significant risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial to remove this package from your projects and regularly audit your dependencies to maintain the integrity of your applications.

See every vulnerability recorded for uafaru-tiut-dtut →

Share this vulnerability

FAQ

The uafaru-tiut-dtut package is an npm package associated with a token reward campaign that has been identified as malicious due to its behavior of modifying package metadata.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code or dependencies.

If you have installed the uafaru-tiut-dtut package, it is recommended to uninstall it immediately and audit your project for any other potentially malicious dependencies.

You can use tools like npm audit to check for vulnerabilities in your project. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

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

How To Fix

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

npm uninstall uafaru-tiut-dtut

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