Malicious Code Injection in rapid_toad_z3n: A Threat to npm Ecosystem

rapid_toad_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96185: Malicious code in rapid_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 package rapid_toad_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code among developers. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages, leading to potential security risks and pollution of the npm registry.

Vulnerability Detail

The vulnerability in rapid_toad_z3n originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically generate and publish derivative packages with randomized names, effectively modifying the package.json file to remove private flags and change version numbers. The malicious payload can lead to a polluted npm registry, where numerous variants of the package are published, making it difficult for developers to identify legitimate packages. This not only compromises the integrity of the npm ecosystem but also poses a risk to applications that may inadvertently use these malicious packages.

How To Fix

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

npm uninstall rapid_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 avoid using the rapid_toad_z3n package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. 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 rapid_toad_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to inflate developer reputation scores. It is crucial for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their applications from potential vulnerabilities.

See every vulnerability recorded for rapid_toad_z3n →

Share this vulnerability

FAQ

rapid_toad_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by publishing numerous derivative packages.

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

It is recommended to remove the rapid_toad_z3n package from your project 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.

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 rapid_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