Malicious Code Injection in verify-ai-aisai Package: npm Vulnerability Overview

verify-ai-aisai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170254: Malicious code in verify-ai-aisai (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The verify-ai-aisai package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is intended to provide AI-related functionalities. However, it has been compromised and is now associated with a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. The malicious nature of this package poses significant risks to developers and their projects.

Vulnerability Detail

The vulnerability in the verify-ai-aisai package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing their projects to further vulnerabilities.

How To Fix

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

npm uninstall verify-ai-aisai

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 avoid using the verify-ai-aisai package and look for alternative packages that provide similar functionalities without the associated risks. Additionally, you can monitor your project for any unauthorized changes to package.json and other critical files.

Conclusion

The verify-ai-aisai package has been identified as a source of malicious code that can compromise your project. It is crucial to remove this package and monitor your dependencies regularly to ensure the security of your applications. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in your software.

See every vulnerability recorded for verify-ai-aisai →

Share this vulnerability

FAQ

The verify-ai-aisai package is an npm package intended for AI-related functionalities but has been compromised with malicious code.

The malicious code modifies your package.json, removes private flags, and generates random package names, leading to potential pollution of the npm registry and risks to your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

You should uninstall the verify-ai-aisai package immediately and check for any updates or patches for your other dependencies.

Yes, you should look for alternative packages that provide similar functionalities without the associated risks of the compromised package.

How To Fix

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

npm uninstall verify-ai-aisai

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