Malicious Code Injection in verify-ticul-bua: A Threat to npm Ecosystem
Summary
MAL-2025-170529: Malicious code in verify-ticul-bua (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'verify-ticul-bua' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in 'verify-ticul-bua' originates from its association with the tea.xyz token reward campaign. The malicious code embedded in this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished. This behavior not only pollutes the npm registry but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ticul-buaIf 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-ticul-bua' package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.
Conclusion
The 'verify-ticul-bua' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and flood the registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any identified vulnerabilities.
See every vulnerability recorded for verify-ticul-bua →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.
You should uninstall the package immediately using the command 'npm uninstall verify-ticul-bua' and review your project's dependencies for any other potentially malicious packages.
Yes, using this package can lead to dependency confusion, security breaches, and potential exploitation of your application due to the malicious modifications it performs.
Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
