Malicious Code Injection in different_mackerel_z3n Package
Summary
MAL-2025-94019: Malicious code in different_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 different_mackerel_z3n package is part of the npm ecosystem, often used in JavaScript applications. It is designed to facilitate various functionalities within web applications. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for legitimate packages to be found. The malicious payload can lead to unauthorized access and manipulation of project dependencies, posing significant risks to application security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall different_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 measure, avoid using the different_mackerel_z3n package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The different_mackerel_z3n package poses significant security risks due to its involvement in a malicious npm campaign. It is essential for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for different_mackerel_z3n →
FAQ
It is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.
The vulnerability can lead to unauthorized changes in your project's dependencies, potentially compromising application security.
You should uninstall the different_mackerel_z3n package immediately and monitor your project for any unusual behavior.
Yes, Vulert can monitor your project for open-source vulnerabilities using just the package-lock.json file, providing real-time alerts.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
