Malicious Code Injection in open_mackerel_z3n: A Threat to npm Users
Summary
MAL-2025-89311: Malicious code in open_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The open_mackerel_z3n package is part of the npm ecosystem, which is widely used for managing JavaScript packages. 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 that automatically generate and publish derivative packages, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in open_mackerel_z3n originates from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, leading to pollution of the npm registry. This behavior can inflate developer reputation scores fraudulently and potentially expose users to further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall open_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 open_mackerel_z3n package from your project by executing: npm uninstall open_mackerel_z3n. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The open_mackerel_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to stay vigilant, regularly update their packages, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for open_mackerel_z3n →
FAQ
open_mackerel_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
This vulnerability can lead to the modification of your package.json file, potentially exposing your application to further malicious activities and compromising its integrity.
If you have installed open_mackerel_z3n, it is crucial to uninstall it immediately and check for any other affected packages.
Yes, you can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
