Malicious Code Detected in verify-ayca-amalaunima: A Threat to npm Ecosystem

verify-ayca-amalaunima Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170365: Malicious code in verify-ayca-amalaunima (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 package 'verify-ayca-amalaunima' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be linked to a token reward campaign that has been flooding the npm registry with malicious packages. These packages often include scripts that automatically generate and publish derivative packages, potentially harming developers' reputations and polluting the registry.

Vulnerability Detail

The vulnerability in 'verify-ayca-amalaunima' originates 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 can lead to the proliferation of harmful packages in the npm registry, affecting developers and users by introducing security risks and potentially malicious code into their applications.

How To Fix

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

npm uninstall verify-ayca-amalaunima

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 measure, you can avoid using the 'verify-ayca-amalaunima' package until a fix is confirmed. Additionally, consider using the following command to remove the package from your project: 'npm uninstall verify-ayca-amalaunima'.

Conclusion

The 'verify-ayca-amalaunima' package poses a significant risk to the npm ecosystem due to its malicious behavior. It is essential for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for verify-ayca-amalaunima →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json files and floods the npm registry with harmful derivatives.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately and check for any updates or patches that may be available.

While specific exploits are not detailed, the behavior of the package suggests it can introduce security risks by polluting the npm registry.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall verify-ayca-amalaunima

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