Malicious Code Injection in consistent_canid_z3n: A Threat to npm Packages
Summary
MAL-2025-93743: Malicious code in consistent_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 package 'consistent_canid_z3n' is part of the npm ecosystem and has been associated with the tea.xyz token reward campaign. This campaign has led to the proliferation of packages that contain scripts designed to manipulate the npm registry. The primary function of these packages is to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.
Vulnerability Detail
The vulnerability in 'consistent_canid_z3n' arises from the inclusion of malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion and the introduction of untrusted code into applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall consistent_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 avoid using 'consistent_canid_z3n' and replace it with alternative packages that provide similar functionality without the associated risks. Review your package-lock.json file to identify and remove any instances of this vulnerable package.
Conclusion
The 'consistent_canid_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with untrusted variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain application security.
See every vulnerability recorded for consistent_canid_z3n →
FAQ
The vulnerability involves malicious code that alters package metadata and publishes untrusted variants to the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Using compromised packages can lead to security breaches, data leaks, and the introduction of malware into your applications.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to your packages.
Remove the package immediately and replace it with a secure alternative. Ensure to audit your code for any potential impacts from the malicious code.
