Malicious Code Injection in uaragifa-afaoti-urufyo Package

uaragifa-afaoti-urufyo Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169501: Malicious code in uaragifa-afaoti-urufyo (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-urufyo package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality, while seemingly innocuous, has been exploited to introduce malicious behavior.

Vulnerability Detail

The vulnerability in the uaragifa-afaoti-urufyo package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to manipulate npm registry metrics. The ramifications include potential pollution of the npm registry and unauthorized access to sensitive data, as the malicious payload can compromise the integrity of projects relying on this package.

How To Fix

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

npm uninstall uaragifa-afaoti-urufyo

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-afaoti-urufyo package from your project by executing the command: 'npm uninstall uaragifa-afaoti-urufyo'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The uaragifa-afaoti-urufyo package contains a significant vulnerability that can compromise the integrity of projects using it. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for future vulnerabilities.

See every vulnerability recorded for uaragifa-afaoti-urufyo →

Share this vulnerability

FAQ

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

The vulnerability can lead to unauthorized modifications in your project's package.json file, potentially compromising its integrity and security.

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

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities without signup at the Vulert playground.

Regularly update your dependencies, use tools like Vulert for monitoring vulnerabilities, and audit your packages to ensure they are from trusted sources.

How To Fix

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

npm uninstall uaragifa-afaoti-urufyo

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