Malicious Code Injection in verify-ticaul-bisusayaa Package
Summary
MAL-2025-170518: Malicious code in verify-ticaul-bisusayaa (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-bisusayaa package is part of the npm ecosystem, primarily used for various JavaScript applications. This package has been identified as part of a broader malicious campaign that aims to exploit npm's publishing capabilities. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for certain token rewards.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the verify-ticaul-bisusayaa package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The origin of this issue is linked to a campaign that floods npm with such packages to exploit the system for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-ticaul-bisusayaaIf 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 this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include verify-ticaul-bisusayaa in any of its dependencies.
Conclusion
The verify-ticaul-bisusayaa package poses a significant risk due to its malicious code that alters essential project files and floods the npm registry. It is imperative to remove this package from your project and monitor for any future vulnerabilities using tools like Vulert.
See every vulnerability recorded for verify-ticaul-bisusayaa →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing system.
The vulnerability can lead to the installation of malicious code that alters your package.json file and pollutes the npm registry, potentially compromising your application's integrity.
You should uninstall the verify-ticaul-bisusayaa package immediately using the command: npm uninstall verify-ticaul-bisusayaa.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities without requiring installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
