Malicious Code Injection in verify-ai-aiusai Package

verify-ai-aiusai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170255: Malicious code in verify-ai-aiusai (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The verify-ai-aiusai package is part of the npm ecosystem, primarily used for AI-related functionalities. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through automated scripts that publish derivative packages with altered metadata.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the verify-ai-aiusai package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.

How To Fix

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

npm uninstall verify-ai-aiusai

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 avoid using the verify-ai-aiusai package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The verify-ai-aiusai package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is essential to take immediate action by removing the package and monitoring your dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your project's security posture.

See every vulnerability recorded for verify-ai-aiusai →

Share this vulnerability

FAQ

The verify-ai-aiusai package is an npm package associated with AI functionalities but has been compromised with malicious code.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can help you identify affected packages.

Using this package can lead to security vulnerabilities, including the risk of your project being polluted with malicious variants and potential reputation damage.

To prevent future vulnerabilities, regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor your projects for vulnerabilities.

If you have used the verify-ai-aiusai package, uninstall it immediately and review your project for any potential security issues. Consider using alternative packages.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall verify-ai-aiusai

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