Malicious Code Injection in verify-ticul-busau Package

verify-ticul-busau Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170531: Malicious code in verify-ticul-busau (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 Penetration testing for web, API and mobile 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-ticul-busau package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods npm with packages designed to manipulate developer reputation scores through automated publishing scripts. This vulnerability poses significant risks to developers and users relying on the integrity of npm packages.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the verify-ticul-busau package, which is linked to the tea.xyz token reward campaign. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can compromise the security and reliability of applications that depend on these packages.

How To Fix

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

npm uninstall verify-ticul-busau

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-ticul-busau package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity of packages before including them in your project.

Conclusion

The verify-ticul-busau package presents a significant security risk due to its malicious code designed to manipulate npm's package ecosystem. It is essential for developers to remove this package from their projects and to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their dependencies.

See every vulnerability recorded for verify-ticul-busau →

Share this vulnerability

FAQ

The verify-ticul-busau package is an npm package that has been identified as malicious, part of a campaign to manipulate developer reputation scores.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the security and reliability of your project by introducing malicious code.

If you have installed the verify-ticul-busau package, you should uninstall it immediately using 'npm uninstall verify-ticul-busau' and check your project for any other affected packages.

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

Yes, you should look for well-reviewed and maintained packages that offer similar functionality but have a proven track record of security.

How To Fix

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

npm uninstall verify-ticul-busau

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