Malicious Code Injection in scientific_coyote_z3n Package
Summary
MAL-2025-108427: Malicious code in scientific_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 scientific_coyote_z3n package is part of the npm ecosystem, typically used for various JavaScript applications. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through automated publishing of derivative packages. This package is particularly vulnerable due to its design, which allows for the manipulation of its metadata and the generation of numerous variants that can pollute the npm registry.
Vulnerability Detail
The vulnerability in the scientific_coyote_z3n package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the automatic republishing of these variants, which can severely impact the integrity of the npm registry and potentially compromise other applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall scientific_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 workaround, you can prevent the installation of the malicious package by using npm's package-lock.json file to lock your dependencies. This will ensure that your application does not inadvertently install the vulnerable version. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The scientific_coyote_z3n package poses a significant risk due to its malicious code that manipulates package metadata and floods the npm registry. It is crucial to take immediate action by uninstalling the package and monitoring your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for scientific_coyote_z3n →
FAQ
scientific_coyote_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the automatic generation and publication of malicious packages, potentially compromising your application's integrity and security.
You should uninstall the scientific_coyote_z3n package immediately and monitor your dependencies for any further vulnerabilities.
Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest versions to mitigate risks.
