Malicious Code Injection in acceptable_mole_dumbs Package

acceptable_mole_dumbs Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99069: Malicious code in acceptable_mole_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The acceptable_mole_dumbs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in the acceptable_mole_dumbs package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the affected package but also leads to the continuous republishing of variants, which can clutter the npm registry and potentially introduce security risks to applications that depend on these packages.

How To Fix

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

npm uninstall acceptable_mole_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 acceptable_mole_dumbs package and replace it with a similar package that does not have known vulnerabilities. Additionally, ensure that your package-lock.json file is monitored for any changes using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The acceptable_mole_dumbs package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the affected package, and utilize monitoring tools like Vulert to safeguard their applications against future threats.

See every vulnerability recorded for acceptable_mole_dumbs →

Share this vulnerability

FAQ

The acceptable_mole_dumbs package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application if it inadvertently depends on affected packages.

You should uninstall the acceptable_mole_dumbs package immediately and monitor your project for any other potentially affected packages.

You can use tools like Vulert, which monitors your package-lock.json file and alerts you in real-time for any open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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