Malicious Code Injection in Unchanged Worm Dumbs Package: npm Vulnerability

unchanged_worm_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110048: Malicious code in unchanged_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 'unchanged_worm_dumbs' package is part of a broader ecosystem that includes various npm packages often associated with token reward campaigns. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is primarily aimed at inflating developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to malicious scripts that alter its metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'unchanged_worm_dumbs' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to significant issues such as unauthorized exposure of sensitive information and degradation of the npm ecosystem. The malicious payload is designed to automate the creation and publication of these compromised packages, thereby affecting the integrity of the npm registry and potentially impacting developers who rely on these packages.

How To Fix

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

npm uninstall unchanged_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 measure, avoid using the 'unchanged_worm_dumbs' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The 'unchanged_worm_dumbs' package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for unchanged_worm_dumbs →

Share this vulnerability

FAQ

It is an npm package associated with malicious activities aimed at inflating developer reputation scores through automated publishing of compromised packages.

The vulnerability can lead to unauthorized exposure of sensitive information and can pollute the npm registry, affecting the integrity of your dependencies.

You should uninstall the 'unchanged_worm_dumbs' package immediately and monitor your project for any other vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

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