Malicious Code Injection in uaragifa-afati-uruuo Package

uaragifa-afati-uruuo Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169522: Malicious code in uaragifa-afati-uruuo (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The uaragifa-afati-uruuo package is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to manipulate npm's registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the uaragifa-afati-uruuo package. This code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, which leads to the continuous republishing of these variants. The result is a polluted npm registry, which can mislead developers and compromise the integrity of the ecosystem. The source of this vulnerability has been traced back to a specific commit identified by the SHA256 hash 018762b2912e82b0b260f333968eb35e8b0d360712e548beb4ca71400cdf23ca.

How To Fix

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

npm uninstall uaragifa-afati-uruuo

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-afati-uruuo package from your project by executing the following command: npm uninstall uaragifa-afati-uruuo. This will help prevent any malicious actions until a secure version is available.

Conclusion

The uaragifa-afati-uruuo package contains malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can further enhance your security posture by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for uaragifa-afati-uruuo →

Share this vulnerability

FAQ

The uaragifa-afati-uruuo package is an npm package linked to a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.

The malicious code modifies your package.json file, removes private flags, and creates random package names, which can lead to a polluted npm registry and affect your project's integrity.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without any signup.

Regularly updating your dependencies and using tools like Vulert to monitor vulnerabilities can help prevent such issues in the future.

If you cannot update the package right away, consider removing it from your project as a temporary measure until a secure version is available.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall uaragifa-afati-uruuo

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