Malicious Code in verify-ticul-biu: A Threat to npm Users

verify-ticul-biu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170524: Malicious code in verify-ticul-biu (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'verify-ticul-biu' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'verify-ticul-biu' originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on this package. The malicious payload can potentially allow unauthorized access to sensitive information and disrupt the normal functioning of dependent applications.

How To Fix

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

npm uninstall verify-ticul-biu

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 workaround, you can manually remove the 'verify-ticul-biu' package from your project by running the command: npm uninstall verify-ticul-biu. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The 'verify-ticul-biu' package poses a significant risk to users within the npm ecosystem due to its malicious behavior. It is essential to take immediate action by removing this package and monitoring your projects for vulnerabilities using tools like Vulert. Staying informed and proactive can help protect your applications from potential threats.

See every vulnerability recorded for verify-ticul-biu →

Share this vulnerability

FAQ

The 'verify-ticul-biu' package is an npm package that has been identified as malicious, associated with the tea.xyz token reward campaign.

This vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's security and integrity.

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

If you have installed 'verify-ticul-biu', it is crucial to uninstall it immediately using the command: npm uninstall verify-ticul-biu.

Yes, Vulert provides a service that monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues.

How To Fix

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

npm uninstall verify-ticul-biu

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