Malicious Code Injection in verify-ayai-augial Package

verify-ayai-augial Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170342: Malicious code in verify-ayai-augial (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 verify-ayai-augial package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of applications relying on it.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the verify-ayai-augial package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores for the tea protocol token rewards. The continuous republishing of these variants pollutes the npm registry, leading to potential security risks for developers and users who may inadvertently install these compromised packages.

How To Fix

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

npm uninstall verify-ayai-augial

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, avoid using the verify-ayai-augial package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The verify-ayai-augial package has been identified as containing malicious code that poses significant risks to applications using it. It is crucial to remove this package and monitor your project for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your software by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for verify-ayai-augial →

Share this vulnerability

FAQ

The verify-ayai-augial package is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can modify your package.json file, remove private flags, and generate random package names, potentially leading to security vulnerabilities in your application.

You should uninstall the verify-ayai-augial package immediately using 'npm uninstall verify-ayai-augial' and monitor your project for any unauthorized changes.

Yes, 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 if your application is affected by visiting the Vulert playground.

Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall verify-ayai-augial

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