Malicious Code Injection in alternative_grouse_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-93206: Malicious code in alternative_grouse_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 'alternative_grouse_z3n' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify the package.json file, removing private flags and altering version numbers, which can lead to the proliferation of unwanted packages in the npm registry.
Vulnerability Detail
The vulnerability in 'alternative_grouse_z3n' originates from its association with a malicious campaign that floods the npm ecosystem with spam packages. The package contains scripts that automatically publish variants with randomized names, effectively polluting the npm registry. This can lead to significant ramifications, including the degradation of the npm ecosystem's integrity, potential security risks for developers using these packages, and the manipulation of developer reputation scores. The malicious payload specifically alters the package.json file to remove private flags and changes version numbers, allowing for continuous republishing of these harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alternative_grouse_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 prevent the installation of this package by using the following command to uninstall it: 'npm uninstall alternative_grouse_z3n'. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can analyze your package-lock.json file for any open-source vulnerabilities.
Conclusion
The 'alternative_grouse_z3n' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and floods the registry with spam. It is crucial for developers to be vigilant, update or remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for alternative_grouse_z3n →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with spam packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.
If you have installed this package, you should uninstall it immediately using 'npm uninstall alternative_grouse_z3n' and monitor your project for any further vulnerabilities.
Yes, using npm packages can pose risks, especially if they are not well-maintained or if they come from untrusted sources. Always verify the integrity of packages before installation.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, helping you maintain a secure application.
