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

uyafu-tuftadat-datut Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170198: Malicious code in uyafu-tuftadat-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 uyafu-tuftadat-datut package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that exploits npm's publishing capabilities. It is designed to generate and publish derivative packages with random names, aiming to inflate developer reputation scores for token rewards associated with the tea.xyz protocol.

Vulnerability Detail

The vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a compromised npm environment, where developers may unknowingly install malicious packages, leading to potential security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall uyafu-tuftadat-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 avoid using the uyafu-tuftadat-datut package and any other packages that may be part of the malicious campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The uyafu-tuftadat-datut package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove any affected packages to maintain the integrity of your projects.

See every vulnerability recorded for uyafu-tuftadat-datut →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to the installation of malicious packages, compromising your project's security and integrity.

You should uninstall the uyafu-tuftadat-datut package immediately and audit your project for any other potentially malicious dependencies.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall uyafu-tuftadat-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