Malicious Code Injection in ordinary_coyote_z3n: A Threat to npm Ecosystem

ordinary_coyote_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95778: Malicious code in ordinary_coyote_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

ordinary_coyote_z3n is an npm package that has been associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages. It aims to inflate developer reputation scores for token rewards, but it has been compromised by malicious actors, making it a potential threat to users and the npm ecosystem.

Vulnerability Detail

The vulnerability in ordinary_coyote_z3n originates from its association with a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on compromised packages, leading to potential security breaches in applications that utilize them.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ordinary_coyote_z3n

If 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 remove the ordinary_coyote_z3n package from your project by executing: npm uninstall ordinary_coyote_z3n. This will prevent any malicious code from executing in your application until a fix is implemented.

Conclusion

The ordinary_coyote_z3n package has been identified as a vector for malicious code that compromises the integrity of the npm ecosystem. Users are advised to uninstall the package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for ordinary_coyote_z3n →

Share this vulnerability

FAQ

ordinary_coyote_z3n is an npm package involved in the tea.xyz token reward campaign, which has been compromised to include malicious code.

The malicious code modifies your package.json file, removes private flags, and can lead to the installation of compromised packages, potentially breaching your application's security.

You should uninstall the ordinary_coyote_z3n package immediately and check for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your packages, use tools like Vulert for monitoring, and review package dependencies to ensure they are from trusted sources.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ordinary_coyote_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback