Malicious Code Injection in bitter_lemur_dumbs: npm Package Vulnerability

bitter_lemur_dumbs Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99987: Malicious code in bitter_lemur_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'bitter_lemur_dumbs' package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and continuously pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which alters the 'package.json' file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and reputation damage.

How To Fix

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

npm uninstall bitter_lemur_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 'bitter_lemur_dumbs' package and instead rely on trusted packages that serve similar functionalities. Additionally, regularly audit your npm packages using tools like 'npm audit' to identify and mitigate vulnerabilities.

Conclusion

The 'bitter_lemur_dumbs' package poses a significant risk due to its malicious behavior of modifying project files and polluting the npm registry. Developers are advised to remove this package and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for bitter_lemur_dumbs →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The vulnerability can lead to the modification of critical files in your project and may expose your application to security risks.

Currently, there is no patched version available for the 'bitter_lemur_dumbs' package.

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

You should uninstall the package immediately and replace it with secure alternatives. Regularly audit your dependencies to ensure security.

How To Fix

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

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