Malicious Code Injection in valid_mackerel_z3n Package
Summary
MAL-2025-97221: Malicious code in valid_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
The valid_mackerel_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package is designed to facilitate certain functionalities within applications that utilize the npm registry. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, potentially compromising the integrity of applications that depend on it.
Vulnerability Detail
The vulnerability stems from the package being associated with 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 inflate developer reputation scores for token rewards, leading to a polluted npm registry. The ramifications include potential security risks for applications using this package, as it can lead to unauthorized access or manipulation of code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall valid_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 valid_mackerel_z3n package from your project by executing the command: npm uninstall valid_mackerel_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The valid_mackerel_z3n package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial to take immediate action by updating or removing the package to safeguard your application from potential threats.
See every vulnerability recorded for valid_mackerel_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
The vulnerability can lead to unauthorized modifications of your application's dependencies, potentially compromising its security.
You should update the package to the latest version or remove it from your project until a secure version is released.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
