Malicious Code Vulnerability in verify-ai-aiusamai Package

verify-ai-aiusamai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170256: Malicious code in verify-ai-aiusamai (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-ai-aiusamai package is part of the npm ecosystem, primarily used for AI verification tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package, like others in the campaign, is designed to inflate developer reputation scores through automated publishing of variants with randomized names.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the verify-ai-aiusamai package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who inadvertently use these packages. The origin of this issue is linked to a broader campaign associated with the tea.xyz token reward initiative.

How To Fix

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

npm uninstall verify-ai-aiusamai

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 workaround, you can monitor your package dependencies using tools like Vulert. Vulert allows you to check your application for vulnerabilities without requiring access to the code or installation. You can use the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.

Conclusion

The verify-ai-aiusamai package contains malicious code that poses significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for verify-ai-aiusamai →

Share this vulnerability

FAQ

It is an npm package used for AI verification tasks but has been compromised with malicious code.

The malicious code can modify your package.json, inflate reputation scores, and pollute the npm registry, posing security risks.

You should uninstall the verify-ai-aiusamai package immediately using 'npm uninstall verify-ai-aiusamai'.

No, it is recommended to avoid using this package altogether as it is part of a malicious campaign.

You can use Vulert, which monitors your package-lock.json for vulnerabilities and alerts you in real-time.

How To Fix

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

npm uninstall verify-ai-aiusamai

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