Malicious Code Injection in passive_coyote_z3n: A Threat to npm Users
Summary
MAL-2025-122448: Malicious code in passive_coyote_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 'passive_coyote_z3n' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'passive_coyote_z3n' 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 leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The origin of this vulnerability is linked to the broader issue of malicious packages flooding the npm ecosystem, specifically targeting developers seeking rewards through the tea protocol.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall passive_coyote_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 'passive_coyote_z3n' package and replace it with a known, secure alternative. Regularly check your package-lock.json file for any unauthorized changes or additions.
Conclusion
The 'passive_coyote_z3n' package poses a significant threat due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications from such vulnerabilities.
See every vulnerability recorded for passive_coyote_z3n →
FAQ
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's integrity and security.
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.
Immediately uninstall the package using 'npm uninstall passive_coyote_z3n' and audit your dependencies for any other malicious packages.
Yes, consider using well-established and trusted packages that provide similar functionality without the associated risks.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from reputable sources.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.