Malicious Code Injection in developing_toad_0xrequest Package

developing_toad_0xrequest Updated 24 Nov 2025

Summary

11/11/2025

Disclosed on

CRITICAL

Severity

No i

Fix available

Critical

Severity

Not published

CVSS Score

MAL-2025-101401: Malicious code in developing_toad_0xrequest (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 Browse

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.

Background

The developing_toad_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the developing_toad_0xrequest package originates from its involvement in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may lead to security breaches in their applications.

How To Fix

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

npm uninstall developing_toad_0xrequest

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 remove the developing_toad_0xrequest package from your project by executing the following command: npm uninstall developing_toad_0xrequest. This will prevent any potential exploitation of the vulnerability until a fix is available.

Conclusion

The developing_toad_0xrequest package contains a significant vulnerability due to its malicious code, which can compromise the npm registry and affect applications using it. It is crucial to update or remove the package to safeguard your projects.

See every vulnerability recorded for developing_toad_0xrequest →