Malicious Code Injection in valid_moose_z3n Package
Summary
MAL-2025-110325: Malicious code in valid_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 valid_moose_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in valid_moose_z3n stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall valid_moose_z3n
If 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, you can prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include valid_moose_z3n by checking your package-lock.json and removing any references to it.
Conclusion
The valid_moose_z3n package poses a significant threat due to its malicious behavior aimed at manipulating the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities effectively. Staying informed and proactive can help maintain the security of your software.
See every vulnerability recorded for valid_moose_z3n →
FAQ
valid_moose_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and its dependencies.
You should uninstall the package immediately using 'npm uninstall valid_moose_z3n' and check for any dependencies that may be affected.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.