Malicious Code Injection in verify-ayic-iamsaha Package

verify-ayic-iamsaha Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170381: Malicious code in verify-ayic-iamsaha (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The verify-ayic-iamsaha package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, its functionality has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability in the verify-ayic-iamsaha package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which employs these tactics to manipulate the npm ecosystem. The ramifications include potential exposure of sensitive data, disruption of package integrity, and degradation of the npm registry's reliability.

How To Fix

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

npm uninstall verify-ayic-iamsaha

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 remove the verify-ayic-iamsaha package from your project by executing the following command: npm uninstall verify-ayic-iamsaha. This will prevent any malicious code from executing while you assess the situation.

Conclusion

The verify-ayic-iamsaha package contains malicious code that poses significant risks to projects using it. It is crucial to take immediate action by updating or removing the package to safeguard your application. Utilizing tools like Vulert can help you monitor for such vulnerabilities in real-time.

See every vulnerability recorded for verify-ayic-iamsaha →

Share this vulnerability

FAQ

The verify-ayic-iamsaha package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.

The malicious code modifies your package.json file, potentially exposing sensitive information and disrupting your project's integrity.

You should update the package to a patched version if available, or uninstall it to prevent any security risks.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring access to the code or installation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall verify-ayic-iamsaha

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