Malicious Code Vulnerability in verify-aai-aisai Package

verify-aai-aisai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170253: Malicious code in verify-aai-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 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-aai-aisai package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to provide specific functionalities within applications. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with randomized names. This vulnerability poses a significant risk to developers and users alike, as it can lead to the pollution of the npm registry and compromise the integrity of applications relying on this package.

Vulnerability Detail

The vulnerability in the verify-aai-aisai package originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also compromises the security and reliability of the npm ecosystem. The continuous republishing of these variants can lead to confusion and potential exploitation by malicious actors.

How To Fix

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

npm uninstall verify-aai-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 remove the verify-aai-aisai package from your project by executing the command: 'npm uninstall verify-aai-aisai'. This will prevent any potential exploitation until a secure version is available.

Conclusion

The verify-aai-aisai package has been identified as a vector for malicious activity within the npm ecosystem. It is essential for developers to be vigilant and take immediate action to update or remove this package to protect their applications from potential exploitation. Utilizing tools like Vulert can aid in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for verify-aai-aisai →

Share this vulnerability

FAQ

The verify-aai-aisai package is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.

This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your application, potentially allowing malicious actors to exploit it.

You should immediately update or uninstall the verify-aai-aisai package to mitigate the risk associated with this vulnerability.

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 use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

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-aai-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