Malicious Code Vulnerability in verify-ayai-auioanygial Package

verify-ayai-auioanygial Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170348: Malicious code in verify-ayai-auioanygial (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The verify-ayai-auioanygial package is part of a broader campaign targeting npm, where malicious packages are created to inflate developer reputation scores for token rewards. This package is designed to manipulate package.json files, removing private flags and altering version numbers, which can lead to significant security risks for developers using it.

Vulnerability Detail

This vulnerability originates from the malicious intent behind the verify-ayai-auioanygial package, which is part of the tea.xyz token reward campaign. The package contains scripts that automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies package.json files to remove private flags and changes version numbers, which can lead to unauthorized access and exploitation of the affected systems.

How To Fix

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

npm uninstall verify-ayai-auioanygial

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 manually edit your package.json file to remove any references to the verify-ayai-auioanygial package and ensure that your project does not depend on any malicious packages. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The verify-ayai-auioanygial package poses a significant security risk due to its malicious intent to manipulate package metadata and inflate developer reputations. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for verify-ayai-auioanygial →

Share this vulnerability

FAQ

It is a malicious npm package designed to inflate developer reputation scores through the automatic generation and publication of derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your project to security risks and dependency issues.

Immediately remove the verify-ayai-auioanygial package from your project and check for any updates or patches that may address the vulnerability.

Yes, Vulert allows you to monitor your package-lock.json for open-source vulnerabilities in real-time without requiring access to your code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall verify-ayai-auioanygial

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