Malicious Code Injection in verify-ayai-auigial Package

verify-ayai-auigial Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170343: Malicious code in verify-ayai-auigial (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-auigial package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the verify-ayai-auigial package originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages.

How To Fix

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

npm uninstall verify-ayai-auigial

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 file to monitor and restrict the use of known vulnerable packages. You can also utilize tools like Vulert to monitor your project for vulnerabilities in real-time without requiring code access. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The verify-ayai-auigial package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial to remove this package and monitor your project for vulnerabilities to maintain security.

See every vulnerability recorded for verify-ayai-auigial →

Share this vulnerability

FAQ

The verify-ayai-auigial package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the installation of malicious code that modifies your package.json file, potentially compromising your application's security.

You should uninstall the verify-ayai-auigial package immediately and check for any dependencies that may be affected.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time.

Regularly update your packages, use trusted sources, and monitor your dependencies with tools like Vulert to prevent similar vulnerabilities.

How To Fix

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

npm uninstall verify-ayai-auigial

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