Malicious Code Injection in verify-taicu-busauna Package

verify-taicu-busauna Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170487: Malicious code in verify-taicu-busauna (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-taicu-busauna package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with various packages. This package, like others in the campaign, is designed to manipulate npm's registry by generating and publishing derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the verify-taicu-busauna package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload is part of a broader trend of autopublish scripts that aim to exploit npm for personal gain.

How To Fix

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

npm uninstall verify-taicu-busauna

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 prevent the installation of the verify-taicu-busauna package by using npm's package-lock.json file to lock down your dependencies. This will help ensure that the malicious package is not inadvertently installed in your project.

Conclusion

The verify-taicu-busauna package contains malicious code that poses a significant risk to the integrity of the npm ecosystem. It is essential to remove this package from your project and monitor for any similar vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for verify-taicu-busauna →

Share this vulnerability

FAQ

The verify-taicu-busauna package is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to pollution of the npm registry and potential security risks.

You should uninstall the verify-taicu-busauna package immediately using the command npm uninstall verify-taicu-busauna.

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 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-taicu-busauna

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