Malicious Code Injection in verify-aya-amilsukxai Package

verify-aya-amilsukxai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170329: Malicious code in verify-aya-amilsukxai (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 Penetration testing for web, API and mobile 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-aya-amilsukxai package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the generation and publication of derivative packages. However, it has been identified as malicious due to its functionality that modifies package metadata and floods the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability in the verify-aya-amilsukxai package originates from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to manipulate developer reputation scores. This behavior can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and potentially compromising their projects.

How To Fix

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

npm uninstall verify-aya-amilsukxai

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-aya-amilsukxai package and any other packages that may be associated with the tea.xyz token reward campaign. Monitor your project for any unintended dependencies that may have been introduced.

Conclusion

The verify-aya-amilsukxai package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor your dependencies for any vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for verify-aya-amilsukxai →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can alter your package metadata and flood the npm registry, making it challenging to find legitimate packages and potentially compromising your project's integrity.

You should uninstall the verify-aya-amilsukxai package immediately and check for any other affected packages in your project.

There is no patch for the verify-aya-amilsukxai package, as it is recommended to remove it entirely from your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall verify-aya-amilsukxai

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