Malicious Code Injection in developing_bat_green-88 Package - npm Vulnerability
Summary
MAL-2025-101392: Malicious code in developing_bat_green-88 (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 developing_bat_green-88 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign targeting developers by flooding the npm registry with derivative packages. Its primary function is to facilitate the tea.xyz token reward campaign, which incentivizes developers to publish more packages, often leading to reputation inflation without genuine contributions.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the developing_bat_green-88 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits developers' desire for recognition.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall developing_bat_green-88If 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 developing_bat_green-88 package and remove it from your dependencies. If you have already installed it, you can uninstall it using the command: npm uninstall developing_bat_green-88.
Conclusion
The developing_bat_green-88 package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for developing_bat_green-88 →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and exposing it to further risks.
You should uninstall the developing_bat_green-88 package immediately and monitor your project for any other vulnerabilities.
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 use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
