Malicious Code Injection in verify-ayica-amua Package

verify-ayica-amua Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170397: Malicious code in verify-ayica-amua (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The verify-ayica-amua package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm environment. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to potential security risks for developers and their projects.

Vulnerability Detail

The vulnerability stems from the package's involvement in a token reward campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting developers' reputations.

How To Fix

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

npm uninstall verify-ayica-amua

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-ayica-amua package and look for alternative packages that provide similar functionalities without the associated risks.

Conclusion

The verify-ayica-amua package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is essential for developers to remove this package from their projects and stay vigilant about monitoring their dependencies for potential vulnerabilities.

See every vulnerability recorded for verify-ayica-amua →

Share this vulnerability

FAQ

The verify-ayica-amua package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to the pollution of the npm registry, which may compromise the integrity of your project's dependencies and affect your reputation as a developer.

You should uninstall the verify-ayica-amua package immediately using the command 'npm uninstall verify-ayica-amua' and monitor your project for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

Regularly update your dependencies, use trusted sources for packages, and utilize tools like Vulert to monitor your projects for vulnerabilities.

How To Fix

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

npm uninstall verify-ayica-amua

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