Malicious Code Injection in uaragifa-afaoti-uyo Package - npm Vulnerability

uaragifa-afaoti-uyo Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169504: Malicious code in uaragifa-afaoti-uyo (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The uaragifa-afaoti-uyo package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity of the npm registry and the potential for malicious exploitation.

Vulnerability Detail

The vulnerability in the uaragifa-afaoti-uyo package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been identified as a source of numerous malicious packages flooding the npm ecosystem.

How To Fix

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

npm uninstall uaragifa-afaoti-uyo

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 uaragifa-afaoti-uyo package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like Vulert, which monitors open-source vulnerabilities in your software without requiring code access or installation.

Conclusion

The uaragifa-afaoti-uyo package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial to remove this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for uaragifa-afaoti-uyo →

Share this vulnerability

FAQ

The uaragifa-afaoti-uyo package is an npm package linked to the tea.xyz token reward campaign, designed to automate the creation and publication of derivative packages.

The vulnerability can lead to the modification of your package.json file, potentially compromising the integrity of your application and introducing security risks.

You should uninstall the uaragifa-afaoti-uyo package immediately and review your dependencies for any other malicious packages.

You can use Vulert to monitor your application for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

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-uyo

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