Malicious Code Injection in residential_worm_dumbs Package - npm Vulnerability

residential_worm_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107940: Malicious code in residential_worm_dumbs (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 residential_worm_dumbs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a tool for developers, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

This vulnerability originates from the malicious intent behind the residential_worm_dumbs package, which contains scripts designed to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to reputation damage and the proliferation of malicious software in the ecosystem.

How To Fix

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

npm uninstall residential_worm_dumbs

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 residential_worm_dumbs package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The residential_worm_dumbs package poses a significant security risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for residential_worm_dumbs →

Share this vulnerability

FAQ

The residential_worm_dumbs package is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and inflating developer reputation scores.

You can check if your application is affected by this vulnerability using Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to use the Vulert playground without any signup.

If you have installed the residential_worm_dumbs package, you should uninstall it immediately using the command npm uninstall residential_worm_dumbs.

Yes, you should look for reputable and well-maintained packages that provide similar functionality without the associated risks. Always verify the package's credibility before installation.

To protect your project, regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and only install packages from trusted sources.

How To Fix

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

npm uninstall residential_worm_dumbs

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