Malicious Code Injection in verify-ticul-biuaua: A Threat to npm Users
Summary
MAL-2025-170526: Malicious code in verify-ticul-biuaua (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-biuaua' is part of a series of npm packages that have been linked to a token reward campaign by tea.xyz. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to alter critical files and continuously pollute the npm registry.
Vulnerability Detail
The vulnerability in 'verify-ticul-biuaua' originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches and loss of control over their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ticul-biuauaIf 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-biuaua' package and check your project for any dependencies that may have included it. Use the following command to check for vulnerable packages: 'npm audit'.
Conclusion
The 'verify-ticul-biuaua' package poses a significant threat due to its malicious code that alters project files and pollutes the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects remain secure.
See every vulnerability recorded for verify-ticul-biuaua →
FAQ
The vulnerability involves malicious code that modifies package.json files and publishes derivative packages to inflate developer reputation scores.
You can use the Vulert platform to monitor your project for vulnerabilities. By analyzing your package-lock.json file, Vulert can alert you in real-time about any open-source vulnerabilities.
You should uninstall the package immediately using 'npm uninstall verify-ticul-biuaua' and check your project for any other affected dependencies.
Yes, Vulert provides a service that monitors your project for vulnerabilities using just the package-lock.json file, allowing you to receive alerts without needing to access the code.
Regularly audit your dependencies using 'npm audit', keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities.
