Malicious Code Injection in closed_canid_z3n Package
Summary
MAL-2025-93592: Malicious code in closed_canid_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 closed_canid_z3n package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the closed_canid_z3n package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall closed_canid_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 prevent the installation of the closed_canid_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will stop npm from installing this package until it is removed or patched.
Conclusion
The closed_canid_z3n package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial to remove this package from your projects and monitor for similar vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for closed_canid_z3n →
FAQ
closed_canid_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted or malicious code.
You should uninstall the closed_canid_z3n package immediately using the command: npm uninstall closed_canid_z3n.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access. You can check your application using the Vulert playground.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review the packages you include in your project.
