Malicious Code Injection in verify-ticaul-bisusayaua Package
Summary
MAL-2025-170519: Malicious code in verify-ticaul-bisusayaua (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 verify-ticaul-bisusayaua package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the generation of derivative packages. However, it has been identified as containing malicious scripts that can compromise the integrity of the npm registry and inflate developer reputation scores.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the verify-ticaul-bisusayaua package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The origin of this issue is linked to a broader campaign that aims to manipulate npm's ecosystem for token rewards, posing risks such as reputation damage for developers and potential security breaches in 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-ticaul-bisusayauaIf 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 malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your package-lock.json file does not include the verify-ticaul-bisusayaua package. You can also use tools like Vulert to monitor for vulnerabilities in your project without requiring code access.
Conclusion
The verify-ticaul-bisusayaua package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain application security.
See every vulnerability recorded for verify-ticaul-bisusayaua →
FAQ
It is an npm package associated with a token reward campaign that has been identified to contain malicious code.
The malicious code can modify your package.json, remove private flags, and republish variants, potentially compromising your application's integrity.
You should uninstall the package immediately using the command npm uninstall verify-ticaul-bisusayaua.
You can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to access the code.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
