Malicious Code Injection in uaragifa-afat-uar Package

uaragifa-afat-uar Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169505: Malicious code in uaragifa-afat-uar (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-afat-uar package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the uaragifa-afat-uar package stems from malicious code that 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, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this vulnerability is linked to automated scripts that are part of a broader scheme to exploit npm for token rewards.

How To Fix

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

npm uninstall uaragifa-afat-uar

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 remove the uaragifa-afat-uar package from your project by executing: npm uninstall uaragifa-afat-uar. This will prevent any malicious scripts from executing until a patched version is available.

Conclusion

The uaragifa-afat-uar package contains a significant vulnerability due to malicious code that alters package metadata and floods the npm registry. It is crucial to uninstall this package and monitor for updates to protect your project from potential risks.

See every vulnerability recorded for uaragifa-afat-uar →

Share this vulnerability

FAQ

The uaragifa-afat-uar package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, potentially exposing your project to security risks and polluting the npm registry.

You should uninstall the package immediately and monitor for any updates or patches that may address the vulnerability.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Vulert is a tool that monitors open-source vulnerabilities in your software using just package-lock.json, providing real-time alerts without requiring code access or installation.

How To Fix

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

npm uninstall uaragifa-afat-uar

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