Malicious Code Injection in yeasty_toad_z3n Package

yeasty_toad_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111285: Malicious code in yeasty_toad_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

The yeasty_toad_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's publishing system, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the yeasty_toad_z3n package stems from its association with a malicious campaign that generates and publishes derivative packages with randomized names. This behavior is designed to inflate developer reputation scores for token rewards in the tea.xyz protocol. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry. This can lead to compromised applications, as developers may unknowingly include these malicious packages in their projects.

How To Fix

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

npm uninstall yeasty_toad_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 measure, you can avoid using the yeasty_toad_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure no malicious packages are included. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The yeasty_toad_z3n package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant about the packages they include in their projects and to utilize tools like Vulert for ongoing monitoring of vulnerabilities. By taking proactive measures, developers can protect their applications from potential threats.

See every vulnerability recorded for yeasty_toad_z3n →

Share this vulnerability

FAQ

Yeasty_toad_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

If included in your application, the yeasty_toad_z3n package can introduce malicious code that compromises the integrity and security of your application.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should uninstall the yeasty_toad_z3n package immediately using 'npm uninstall yeasty_toad_z3n' and audit your other dependencies for similar vulnerabilities.

Yes, regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall yeasty_toad_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