Malicious Code Injection in modest_toad-strongdev Package

modest_toad-strongdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105940: Malicious code in modest_toad-strongdev (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 modest_toad-strongdev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate its own metadata and publish derivatives to inflate developer reputation scores, making it a significant threat to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which deploys malicious scripts (auto.js, autopublish.js, etc.) to alter the package.json file. These scripts remove private flags, change version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the security of the affected systems but also undermines the trustworthiness of the npm ecosystem.

How To Fix

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

npm uninstall modest_toad-strongdev

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 file to lock down your dependencies. Ensure that your project does not include the modest_toad-strongdev package in the package.json file.

Conclusion

The modest_toad-strongdev package poses a significant security risk due to its malicious code designed to manipulate npm registry data. Users are advised to uninstall this package immediately and monitor their projects for any dependencies that may be affected. Utilizing tools like Vulert can help maintain the integrity of your software by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for modest_toad-strongdev →

Share this vulnerability

FAQ

The vulnerability can lead to unauthorized modifications of your project's dependencies and the potential for malicious code execution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing the package-lock.json file. Visit Vulert Scanner to check your application without signup.

There is no patch for the modest_toad-strongdev package due to its malicious nature. The best course of action is to uninstall it.

You should review your dependencies and replace any that rely on the modest_toad-strongdev package with secure alternatives.

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 modest_toad-strongdev

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