Malicious Code Injection in diverse_coyote-strongdev Package

diverse_coyote-strongdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101672: Malicious code in diverse_coyote-strongdev (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The diverse_coyote-strongdev package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate the generation and publication of derivative packages, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the diverse_coyote-strongdev package stems from its association with malicious scripts designed to inflate developer reputation scores through the automatic generation of derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names, leading to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall diverse_coyote-strongdev

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 avoid using the diverse_coyote-strongdev package until a secure version is released. Additionally, you can monitor your project's dependencies using tools like Vulert, which checks for vulnerabilities in your package-lock.json file. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without any signup.

Conclusion

The diverse_coyote-strongdev package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is essential for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for diverse_coyote-strongdev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious scripts.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You should update the package to a patched version or remove it from your project to mitigate risks.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall diverse_coyote-strongdev

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