Malicious Code Vulnerability in Toxic Coyote Dumbs Package

toxic_coyote_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109790: Malicious code in toxic_coyote_dumbs (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

The 'toxic_coyote_dumbs' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the 'toxic_coyote_dumbs' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior pollutes the npm registry and can significantly impact developers by inflating reputation scores fraudulently. The malicious payload is designed to exploit the npm ecosystem, making it a serious concern for developers relying on package integrity.

How To Fix

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

npm uninstall toxic_coyote_dumbs

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 workaround, you can monitor your project for any unauthorized changes to package.json and regularly audit your dependencies using npm audit. Additionally, consider using tools like Vulert to monitor for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'toxic_coyote_dumbs' package contains malicious code that poses a significant threat to the integrity of npm projects. It is crucial to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for toxic_coyote_dumbs →

Share this vulnerability

FAQ

The 'toxic_coyote_dumbs' package is an npm package involved in a token reward campaign that automates the generation of derivative packages.

The malicious code modifies your package.json, removes private flags, and generates random package names, which can lead to reputation inflation and registry pollution.

No, there is currently no patched version of the 'toxic_coyote_dumbs' package available. The recommended action is to uninstall it.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application.

If you have installed the 'toxic_coyote_dumbs' package, you should uninstall it immediately using the command: npm uninstall toxic_coyote_dumbs.

How To Fix

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

npm uninstall toxic_coyote_dumbs

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