Malicious Code Vulnerability in verify-ain-us Package

verify-ain-us Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170316: Malicious code in verify-ain-us (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-ain-us 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 various scripts that automate the generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the verify-ain-us package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for the tea protocol token rewards. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall verify-ain-us

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-ain-us package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The verify-ain-us package has been identified as containing malicious code that compromises the security of the npm ecosystem. It is essential for developers to remove this package from their projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.

See every vulnerability recorded for verify-ain-us →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file, potentially exposing your project to security vulnerabilities and affecting the integrity of your npm dependencies.

If you have installed the verify-ain-us package, it is crucial to remove it immediately and check for any unauthorized changes in your project files.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without requiring access to the code or installation.

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

How To Fix

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

npm uninstall verify-ain-us

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