Malicious Code Injection in verify-ayai-auioanyaugial Package

verify-ayai-auioanyaugial Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170347: Malicious code in verify-ayai-auioanyaugial (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The verify-ayai-auioanyaugial package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate the npm registry and inflate developer reputation scores through automated scripts.

Vulnerability Detail

This vulnerability originates from the malicious intent behind the verify-ayai-auioanyaugial package, which contains scripts that modify the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. The ramifications include potential exposure of sensitive information, unauthorized package modifications, and the risk of developers unknowingly using compromised packages.

How To Fix

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

npm uninstall verify-ayai-auioanyaugial

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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Additionally, you can use the following command to uninstall the package: npm uninstall verify-ayai-auioanyaugial.

Conclusion

The verify-ayai-auioanyaugial package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for verify-ayai-auioanyaugial →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious scripts.

The vulnerability can lead to unauthorized modifications of your package.json file and potential exposure of sensitive information.

You should uninstall the package immediately and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with security advisories.

How To Fix

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

npm uninstall verify-ayai-auioanyaugial

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