Malicious Code Injection in hungry_mule_dumbs Package - npm Vulnerability

hungry_mule_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103844: Malicious code in hungry_mule_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 'hungry_mule_dumbs' package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign on npm. These packages are designed to manipulate the npm registry by automatically generating and publishing numerous derivative packages with randomized names. This activity aims to inflate developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability in the 'hungry_mule_dumbs' package arises from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall hungry_mule_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 'hungry_mule_dumbs' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unexpected changes in the package.json file.

Conclusion

The 'hungry_mule_dumbs' package poses a significant risk to the npm ecosystem due to its malicious behavior. It is essential to remove this package from your projects and monitor for any potential impacts. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for hungry_mule_dumbs →

Share this vulnerability

FAQ

The 'hungry_mule_dumbs' package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the automatic generation and publishing of derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that alters your package.json file and pollutes the npm registry with unwanted packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without needing to sign up.

If you have installed the 'hungry_mule_dumbs' package, you should uninstall it immediately using 'npm uninstall hungry_mule_dumbs' and check for any dependencies that may be affected.

Yes, you should look for alternative packages that provide similar functionality without the risks associated with the 'hungry_mule_dumbs' package.

How To Fix

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

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