Malicious Code Injection in Productive Earthworm Dumbs Package

productive_earthworm_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107305: Malicious code in productive_earthworm_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The 'productive_earthworm_dumbs' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. Its functionality is compromised by malicious scripts that modify package metadata, leading to potential security risks.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the 'productive_earthworm_dumbs' package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security breaches and reputational damage for developers. The malicious payload can also facilitate unauthorized access to sensitive data or systems, making it critical to address this issue promptly.

How To Fix

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

npm uninstall productive_earthworm_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 prevent the execution of the malicious scripts by setting up a strict npm policy that disallows the installation of untrusted packages. You can do this by adding the following line to your .npmrc file: 'strict-ssl=true'. This will help mitigate the risk until the package is removed or patched.

Conclusion

The 'productive_earthworm_dumbs' package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial to uninstall this package and monitor your project for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for productive_earthworm_dumbs →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, potentially exposing your project to security risks and polluting the npm registry.

You should uninstall the package immediately using 'npm uninstall productive_earthworm_dumbs' and check for any other vulnerabilities in your dependencies.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

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

How To Fix

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

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