Malicious Code Injection in conservative_loon_beige-42: npm Package Vulnerability
Summary
MAL-2025-100869: Malicious code in conservative_loon_beige-42 (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 conservative_loon_beige-42 is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the publication of derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, contributing to registry pollution.
Vulnerability Detail
The vulnerability stems from the package's inclusion in a malicious campaign that utilizes scripts to automatically generate and publish numerous derivative packages. This results in the modification of package.json files to remove private flags, alter version numbers, and create random package names. The continuous republishing of these variants can lead to significant pollution of the npm registry, potentially affecting developers' ability to find legitimate packages and compromising the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall conservative_loon_beige-42If 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 this package by removing it from your dependencies. Use the following command to uninstall the package: npm uninstall conservative_loon_beige-42.
Conclusion
The conservative_loon_beige-42 package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish itself. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for conservative_loon_beige-42 →
FAQ
The malicious code modifies package.json files to remove private flags and generates random package names, leading to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.
If you have installed conservative_loon_beige-42, it is crucial to uninstall it immediately and monitor your project for any unusual behavior.
Yes, using this package can lead to security vulnerabilities, including the risk of your project being associated with malicious activities and the potential for registry pollution.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
