Malicious Code Injection in uyafru-tut-datut Package

uyafru-tut-datut Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170191: Malicious code in uyafru-tut-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The uyafru-tut-datut package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods npm with packages designed to inflate developer reputation scores through automated scripts. This package, like others in the campaign, modifies critical files and repackages itself under random names, posing a significant risk to developers and their projects.

Vulnerability Detail

The vulnerability originates from the uyafru-tut-datut package being part of a malicious token reward campaign. It contains scripts that modify 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 can pollute the npm registry and compromise the integrity of projects relying on this package. The malicious payload can potentially expose sensitive information and disrupt the normal functioning of applications that depend on it.

How To Fix

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

npm uninstall uyafru-tut-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 workaround, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that you do not install any packages that are not explicitly listed in your package-lock.json file.

Conclusion

The uyafru-tut-datut package poses a significant risk due to its malicious code that modifies essential project files and repackages itself. It is crucial for developers to uninstall this package and monitor their dependencies to maintain the integrity of their applications.

See every vulnerability recorded for uyafru-tut-datut →

Share this vulnerability

FAQ

The uyafru-tut-datut package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

This vulnerability can lead to the modification of your package.json file, potentially exposing sensitive information and causing disruptions in your application.

If you have installed the uyafru-tut-datut package, you should uninstall it immediately using 'npm uninstall uyafru-tut-datut'.

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software using just package-lock.json.

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

How To Fix

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

npm uninstall uyafru-tut-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