Malicious Code Injection in uaragifa-afaoti-ufyo Package

uaragifa-afaoti-ufyo Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169495: Malicious code in uaragifa-afaoti-ufyo (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The uaragifa-afaoti-ufyo package is part of the npm ecosystem, often used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with packages that manipulate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, making it susceptible to malicious exploitation.

Vulnerability Detail

The vulnerability in the uaragifa-afaoti-ufyo package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of these malicious packages.

How To Fix

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

npm uninstall uaragifa-afaoti-ufyo

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 workaround, you can monitor your project for any instances of the uaragifa-afaoti-ufyo package and remove it immediately. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The uaragifa-afaoti-ufyo package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for uaragifa-afaoti-ufyo →

Share this vulnerability

FAQ

The uaragifa-afaoti-ufyo package is an npm package associated with the tea.xyz token reward campaign, known for generating and publishing malicious packages.

This vulnerability can lead to the pollution of the npm registry and may compromise your application's integrity by introducing malicious code.

You should uninstall the uaragifa-afaoti-ufyo package immediately using the command: npm uninstall uaragifa-afaoti-ufyo.

Yes, regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of 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 uaragifa-afaoti-ufyo

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