Malicious Code Injection in cheap_moose_z3n: A Threat to npm Users
Summary
MAL-2025-100361: Malicious code in cheap_moose_z3n (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 'cheap_moose_z3n' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. This campaign has led to the creation of numerous packages that are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. These packages often contain scripts that manipulate their own metadata and can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'cheap_moose_z3n' originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, thereby polluting the npm registry and potentially compromising the integrity of the ecosystem. The malicious payload can lead to unauthorized access and manipulation of project dependencies, posing a risk to developers and users relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cheap_moose_z3nIf 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 remove the 'cheap_moose_z3n' package from your project by executing the following command: 'npm uninstall cheap_moose_z3n'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The 'cheap_moose_z3n' package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish variants. It is crucial for developers to take immediate action by updating or removing the package to protect their projects. Utilizing tools like Vulert can enhance your ability to monitor and manage open-source vulnerabilities effectively.
See every vulnerability recorded for cheap_moose_z3n →
FAQ
The primary risk is the potential for unauthorized modifications to your project's dependencies, which can lead to security vulnerabilities and instability.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By simply uploading your package-lock.json file, you can receive real-time alerts for any vulnerabilities.
If immediate updates are not possible, consider removing the package from your project as a temporary measure to mitigate risk.
While specific alternatives depend on your project's requirements, consider researching other npm packages that offer similar functionality without the associated risks.
Vulert provides a simple way to monitor your dependencies for vulnerabilities using your package-lock.json file, allowing you to stay informed and secure without needing to access the code directly.
