Malicious Code Vulnerability in verify-tayic-iam Package

verify-tayic-iam Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170498: Malicious code in verify-tayic-iam (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The verify-tayic-iam package is part of the npm ecosystem, designed to facilitate identity and access management in applications. However, it has been compromised as part of a broader malicious campaign that targets npm packages, leading to significant security concerns. This package is associated with the tea.xyz token reward initiative, which has been linked to the proliferation of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the verify-tayic-iam package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores and pollute the npm registry with derivative packages. The malicious payload can lead to unauthorized access, data leakage, and compromise the integrity of applications relying on this package.

How To Fix

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

npm uninstall verify-tayic-iam

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-iam package and look for alternative libraries that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The verify-tayic-iam package has been compromised, posing significant security risks to applications that utilize it. Immediate action is required to remove the package and monitor for vulnerabilities using tools like Vulert. Staying informed and proactive is essential for maintaining application security.

See every vulnerability recorded for verify-tayic-iam →

Share this vulnerability

FAQ

The verify-tayic-iam package is an npm package used for identity and access management in applications.

The malicious code can modify your package.json, remove private flags, and introduce unauthorized changes, potentially leading to security breaches.

You should uninstall the verify-tayic-iam package immediately and look for alternative solutions.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall verify-tayic-iam

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