Malicious Code Injection in verify-ayca-amilsukaoxmai Package

verify-ayca-amilsukaoxmai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170378: Malicious code in verify-ayca-amilsukaoxmai (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-ayca-amilsukaoxmai package is part of the npm ecosystem and has been identified as a component of a token reward campaign associated with tea.xyz. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been compromised to include malicious scripts that alter its behavior and impact the npm registry.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the verify-ayca-amilsukaoxmai package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of variants. The primary risk is the pollution of the npm registry, which can affect other developers and projects relying on npm packages. This malicious activity is part of a broader scheme to exploit the npm ecosystem for fraudulent gains.

How To Fix

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

npm uninstall verify-ayca-amilsukaoxmai

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, avoid using the verify-ayca-amilsukaoxmai package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json file.

Conclusion

The verify-ayca-amilsukaoxmai package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for verify-ayca-amilsukaoxmai →

Share this vulnerability

FAQ

It is an npm package involved in a token reward campaign that has been compromised to include malicious code.

The malicious code modifies your package.json, removes private flags, and can lead to the pollution of the npm registry, potentially affecting your project's dependencies.

You should uninstall the package immediately using 'npm uninstall verify-ayca-amilsukaoxmai' and check for alternative packages.

You can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to install any software.

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

How To Fix

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

npm uninstall verify-ayca-amilsukaoxmai

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