Malicious Code Detected in ujodzb-devapptea: A Threat to npm Users

ujodzb-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109961: Malicious code in ujodzb-devapptea (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

ujodzb-devapptea is a package associated with the tea.xyz token reward campaign, which has gained notoriety for flooding the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. The primary function of ujodzb-devapptea is to serve as a conduit for these malicious activities, posing significant risks to developers and users alike.

Vulnerability Detail

The ujodzb-devapptea package contains malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also exposes developers to potential security risks and reputational damage.

How To Fix

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

npm uninstall ujodzb-devapptea

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 ujodzb-devapptea and any packages that depend on it. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities in your project.

Conclusion

The ujodzb-devapptea package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for ujodzb-devapptea →

Share this vulnerability

FAQ

ujodzb-devapptea is a malicious npm package linked to the tea.xyz token reward campaign, designed to manipulate developer reputation scores.

The vulnerability can compromise your project's integrity by introducing malicious code that alters package configurations and floods the npm registry with unwanted packages.

You should immediately uninstall the package using 'npm uninstall ujodzb-devapptea' and check for any dependencies that may rely on it.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Yes, 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 ujodzb-devapptea

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