Malicious Code Injection in billa-95: A Threat to npm Ecosystem
Summary
MAL-2025-153749: Malicious code in billa-95 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'billa-95' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, 'billa-95' has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in 'billa-95' originates from its involvement in the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for legitimate packages to be found. The malicious payload can lead to unauthorized access and manipulation of projects that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall billa-95If 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 measure, avoid using 'billa-95' and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The billa-95 package poses a significant security risk due to its malicious code that manipulates npm's publishing system. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining a secure development environment.
See every vulnerability recorded for billa-95 →
FAQ
The billa-95 package contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert to monitor your project for vulnerabilities. Simply upload your package-lock.json file to check for any affected packages.
You should uninstall the package immediately using 'npm uninstall billa-95' and check for any alternative packages.
Currently, there are no patches available for billa-95. It is recommended to remove the package entirely.
Vulert uses your package-lock.json file to monitor and alert you in real-time about open-source vulnerabilities, helping you maintain secure applications.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
