Malicious Code Injection in slow_toad_z3n: A Threat to npm Ecosystem

slow_toad_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90693: Malicious code in slow_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 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 package slow_toad_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and distribution of JavaScript applications. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with harmful scripts.

Vulnerability Detail

The vulnerability in slow_toad_z3n originates from its association with the tea.xyz token reward campaign, which has led to the proliferation of malicious packages in the npm registry. The malicious code within this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry and potentially compromising the integrity of other packages. This can lead to severe ramifications, including the loss of developer reputation and the introduction of security risks into dependent applications.

How To Fix

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

npm uninstall slow_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 workaround, you can prevent the installation of this malicious package by using npm's package-lock.json to lock your dependencies. Additionally, consider using the following command to audit your dependencies for vulnerabilities: npm audit.

Conclusion

The slow_toad_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the registry. It is crucial for developers to be vigilant and take immediate action to remove this package and monitor their dependencies for vulnerabilities.

See every vulnerability recorded for slow_toad_z3n →

Share this vulnerability

FAQ

slow_toad_z3n is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should remove the slow_toad_z3n package from your project immediately and monitor for any updates or patches.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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