Malicious Code Injection in controlled_moose_z3n Package
Summary
MAL-2025-93783: Malicious code in controlled_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 controlled_moose_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores through automated publishing.
Vulnerability Detail
The vulnerability in the controlled_moose_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The malicious payload can compromise the integrity of the npm registry and potentially affect developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall controlled_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 controlled_moose_z3n package from your project by executing: npm uninstall controlled_moose_z3n. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The controlled_moose_z3n package poses a significant risk due to its malicious code that alters package metadata and inflates developer reputation scores. It is essential to take immediate action by updating or removing the package to safeguard your project and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for controlled_moose_z3n →
FAQ
controlled_moose_z3n is an npm package that is part of a malicious campaign aimed at manipulating npm registry metadata.
This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should uninstall the controlled_moose_z3n package immediately and check for any updates or patches for your other dependencies.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
