Malicious Code Injection in verify-ayali-gaka Package

verify-ayali-gaka Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170360: Malicious code in verify-ayali-gaka (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-ayali-gaka package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated publishing of derivative packages, which can lead to significant security risks for applications that depend on it.

Vulnerability Detail

The vulnerability in the verify-ayali-gaka package stems from its malicious code that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This behavior can lead to unintended consequences, such as the introduction of insecure code into applications and the potential for exploitation by malicious actors.

How To Fix

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

npm uninstall verify-ayali-gaka

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 prevent the installation of the verify-ayali-gaka package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using npm audit to identify and address vulnerabilities in your dependencies.

Conclusion

The verify-ayali-gaka package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to protect their applications.

See every vulnerability recorded for verify-ayali-gaka →

Share this vulnerability

FAQ

The verify-ayali-gaka package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the introduction of insecure code, potentially allowing malicious actors to exploit your application.

You should remove the verify-ayali-gaka package from your project and check for any other affected packages in your dependencies.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

Regularly audit your dependencies using tools like npm audit and consider using automated monitoring services like Vulert to stay informed about vulnerabilities.

How To Fix

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

npm uninstall verify-ayali-gaka

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