Malicious Code Injection in verify-ayic-iamha Package

verify-ayic-iamha Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170380: Malicious code in verify-ayic-iamha (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-iamha package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated scripts that publish derivative packages with randomized names.

Vulnerability Detail

The vulnerability stems from the malicious code embedded in the verify-ayic-iamha package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards, leading to pollution of the npm registry and potential security risks for users who inadvertently install these packages.

How To Fix

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

npm uninstall verify-ayic-iamha

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, avoid using the verify-ayic-iamha package and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The verify-ayic-iamha package poses a significant security risk due to its malicious code that alters project dependencies. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security. Utilizing tools like Vulert can help in identifying and managing such risks effectively.

See every vulnerability recorded for verify-ayic-iamha →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to the installation of malicious code that modifies your project's dependencies and potentially exposes it to further security risks.

You should uninstall the verify-ayic-iamha package immediately and monitor your project for any unusual behavior.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using 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 any signup.

How To Fix

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

npm uninstall verify-ayic-iamha

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