Malicious Code Injection in verify-tical-bisya: A Threat to npm Ecosystem
Summary
MAL-2025-170514: Malicious code in verify-tical-bisya (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-tical-bisya' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages designed to inflate developer reputation scores. These packages often contain scripts that automate the generation and publication of derivative packages, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in 'verify-tical-bisya' stems from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to pollute the npm registry and can lead to unauthorized access and manipulation of projects that depend on this package. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which exploits npm's package management system for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-tical-bisyaIf 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 'verify-tical-bisya' and replace it with a trusted alternative package that provides similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes in the package.json file.
Conclusion
The 'verify-tical-bisya' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for verify-tical-bisya →
FAQ
The main issue is that it contains malicious code that modifies package.json and floods the npm registry with unauthorized packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall verify-tical-bisya' and review your project for any unauthorized changes.
Yes, you should look for trusted packages that offer similar functionality without the security risks associated with verify-tical-bisya.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
