Malicious Code Injection in verify-technical-bisa: npm Package Vulnerability
Summary
MAL-2025-170508: Malicious code in verify-technical-bisa (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-technical-bisa' package is part of a broader campaign associated with the tea.xyz token reward system. It is designed to facilitate the generation and publication of derivative packages on the npm registry. This package, like others in the campaign, is equipped with scripts that automate the publishing process, potentially leading to the proliferation of malicious variants that can compromise developer reputation and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'verify-technical-bisa' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-technical-bisaIf 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-technical-bisa' package altogether. If it is a dependency of another package, consider removing that package or finding an alternative that does not rely on it.
Conclusion
The 'verify-technical-bisa' package is a clear example of how malicious actors can exploit open-source ecosystems. By understanding the nature of this vulnerability and taking proactive steps to remove affected packages, developers can safeguard their applications and contribute to a healthier software environment.
See every vulnerability recorded for verify-technical-bisa →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
If your application uses the 'verify-technical-bisa' package, it may inadvertently include malicious code that can compromise security and lead to potential data breaches.
You should uninstall the 'verify-technical-bisa' package immediately and check for any other dependencies that may be affected.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
