Malicious Code Injection in verify-taic-alu: A Threat to npm Users

verify-taic-alu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170468: Malicious code in verify-taic-alu (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-taic-alu' 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 and deployment of applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, potentially compromising the integrity of projects that depend on it.

Vulnerability Detail

The vulnerability in 'verify-taic-alu' stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to reputation inflation for malicious actors and pollute the npm registry, making it difficult for developers to find legitimate packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.

How To Fix

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

npm uninstall verify-taic-alu

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 measure, you can avoid using the 'verify-taic-alu' package and any other packages that are part of the tea.xyz campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The 'verify-taic-alu' package poses a significant risk to npm users due to its malicious behavior. It is essential to remove this package from your projects and adopt best practices for dependency management to safeguard your applications from potential threats.

See every vulnerability recorded for verify-taic-alu →

Share this vulnerability

FAQ

The 'verify-taic-alu' package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can also check your application against the Vulert playground without any signup.

If you have installed 'verify-taic-alu', you should uninstall it immediately using the command 'npm uninstall verify-taic-alu'.

There are no patches available for 'verify-taic-alu' as it is recommended to remove the package entirely due to its malicious nature.

To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and keep your packages updated to their latest versions.

How To Fix

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

npm uninstall verify-taic-alu

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