Malicious Code Injection in verify-ayic-iamsasiha Package

verify-ayic-iamsasiha Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170382: Malicious code in verify-ayic-iamsasiha (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 Your last release was probably never penetration tested 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-ayic-iamsasiha package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the verify-ayic-iamsasiha package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It is designed to automatically publish derivative packages, thereby inflating developer reputation scores for token rewards in the tea.xyz campaign. The ramifications include the pollution of the npm registry with potentially harmful packages, which can lead to security breaches in applications that unknowingly depend on these malicious packages.

How To Fix

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

npm uninstall verify-ayic-iamsasiha

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 prevent the installation of the malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include verify-ayic-iamsasiha in the package-lock.json. Additionally, consider using tools like Vulert to monitor and alert for vulnerabilities in your dependencies.

Conclusion

The verify-ayic-iamsasiha package poses a significant security risk due to its malicious code designed to exploit npm's publishing system. It is crucial for developers to be vigilant about their dependencies and to utilize tools like Vulert for real-time monitoring of vulnerabilities. Uninstalling the affected package and keeping dependencies updated are essential steps in maintaining application security.

See every vulnerability recorded for verify-ayic-iamsasiha →

Share this vulnerability

FAQ

The verify-ayic-iamsasiha package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code can modify your package.json, remove private flags, and publish harmful variants, potentially leading to security vulnerabilities in your application.

You should uninstall the verify-ayic-iamsasiha package immediately and check for any dependencies that may have been affected.

Regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall verify-ayic-iamsasiha

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