Malicious Code Injection in horrible_boa_dumbs Package - npm Vulnerability

horrible_boa_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103791: Malicious code in horrible_boa_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 'horrible_boa_dumbs' package is part of a series of malicious packages that emerged during 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 behavior includes modifying the package.json file to remove private flags and changing version numbers, which can lead to significant pollution of the npm registry.

Vulnerability Detail

This vulnerability originates from the 'horrible_boa_dumbs' package, which contains scripts that automatically publish derivative packages with random names. The malicious payload alters the package.json file, removing private flags and changing version numbers, allowing the package to continuously republish variants. This can lead to reputation inflation for developers and pollution of the npm registry, potentially affecting the integrity of the ecosystem.

How To Fix

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

npm uninstall horrible_boa_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 remove the 'horrible_boa_dumbs' package from your project by executing the command: 'npm uninstall horrible_boa_dumbs'. This will prevent any malicious activity associated with this package until a patch is available.

Conclusion

The 'horrible_boa_dumbs' package presents a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to take immediate action to remove this package and monitor for updates to protect your application and maintain the integrity of the software ecosystem.

See every vulnerability recorded for horrible_boa_dumbs →

Share this vulnerability

FAQ

The 'horrible_boa_dumbs' package is a malicious npm package that is part of a campaign to inflate developer reputation scores by automatically publishing derivative packages.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing unwanted packages.

You should uninstall the 'horrible_boa_dumbs' package and monitor for any updates or patches that may be released.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

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

How To Fix

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

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