Malicious Code Injection in primary_canid_z3n Package
Summary
MAL-2025-96015: Malicious code in primary_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 primary_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 harmful packages. This package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant security risks.
Vulnerability Detail
The vulnerability in the primary_canid_z3n package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also exposes developers to potential security threats as these malicious packages can pollute the ecosystem and lead to unintended consequences in applications that rely on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall primary_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 measure, you can avoid using the primary_canid_z3n package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.
Conclusion
The primary_canid_z3n package poses a significant security risk due to its malicious code injection practices. It is crucial for developers to be vigilant about their dependencies and take immediate action to remove any affected packages. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for primary_canid_z3n →
FAQ
It 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 introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the primary_canid_z3n package immediately and review your project for any other potentially harmful dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
