Malicious Code Injection in verify-aysali-anais Package

verify-aysali-anais Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170428: Malicious code in verify-aysali-anais (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-aysali-anais package is part of the npm ecosystem, primarily used for various JavaScript applications. This package has been identified as part of a broader malicious campaign targeting npm, where it is utilized to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises its integrity and poses significant risks to developers and users alike.

Vulnerability Detail

The vulnerability in the verify-aysali-anais package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to pollute the npm registry and can lead to unauthorized access, data leaks, and the potential for further exploitation of dependent applications. The malicious payload is embedded within the package, making it a significant threat to any project that includes it.

How To Fix

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

npm uninstall verify-aysali-anais

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-aysali-anais package and replace it with a trusted alternative. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The verify-aysali-anais package poses a significant risk due to its malicious code that modifies project files and inflates developer reputation scores. Immediate action is required to remove this package and safeguard your application from potential threats. Regular monitoring and auditing of dependencies are essential to maintain security.

See every vulnerability recorded for verify-aysali-anais →

Share this vulnerability

FAQ

The verify-aysali-anais package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

This vulnerability can lead to unauthorized modifications of your package.json file, potentially allowing for further exploitation and data leaks.

You should uninstall the verify-aysali-anais package immediately and audit your project for other potentially malicious packages.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall verify-aysali-anais

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