Malicious Code Injection in verify-tayic-aibamu Package

verify-tayic-aibamu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170491: Malicious code in verify-tayic-aibamu (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-tayic-aibamu package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities related to token rewards but has been compromised to include malicious scripts that can affect the integrity of the npm registry. The package's primary function is to manage token rewards, but its malicious modifications can lead to severe consequences for developers using it.

Vulnerability Detail

The vulnerability in the verify-tayic-aibamu package stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only inflates developer reputation scores fraudulently but also pollutes the npm registry, potentially affecting other developers and applications relying on npm packages.

How To Fix

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

npm uninstall verify-tayic-aibamu

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-tayic-aibamu 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-tayic-aibamu package has been identified as containing malicious code that can compromise the integrity of your npm projects. It is essential to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your software.

See every vulnerability recorded for verify-tayic-aibamu →

Share this vulnerability

FAQ

The verify-tayic-aibamu package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign, which has been compromised to include malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to the pollution of the npm registry and affect your project's integrity.

You should uninstall the verify-tayic-aibamu package immediately using the command npm uninstall verify-tayic-aibamu and check for any updates or patches for your other dependencies.

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

Yes, you should look for alternative packages that provide similar functionalities without the associated risks. Always ensure to review the package's reputation and security before installation.

How To Fix

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

npm uninstall verify-tayic-aibamu

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