Malicious Code Exploit in managerial_mackerel_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-105588: Malicious code in managerial_mackerel_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
managerial_mackerel_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automated generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify essential files and continuously pollute the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability in managerial_mackerel_z3n originates from its design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This behavior not only modifies the package.json file by removing private flags and changing version numbers but also leads to the creation of numerous Indonesian-themed package names. The continuous republishing of these variants can significantly clutter the npm registry, making it difficult for developers to find legitimate packages and potentially leading to security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall managerial_mackerel_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 managerial_mackerel_z3n package from your project by executing the command: npm uninstall managerial_mackerel_z3n. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The managerial_mackerel_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to inflate developer reputation scores. It is crucial for developers to be aware of such vulnerabilities, take immediate action to remove affected packages, and utilize tools like Vulert for ongoing monitoring.
See every vulnerability recorded for managerial_mackerel_z3n →
FAQ
managerial_mackerel_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially exposing your project to security risks.
If you have installed managerial_mackerel_z3n, you should uninstall it immediately and check for any updates or patches for your other dependencies.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without signing up.
Detailed information about this vulnerability can be found in the official npm registry and security advisories related to the managerial_mackerel_z3n package.
