Malicious Code Injection in 'voluntary_harrier_dumbs' Package

voluntary_harrier_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110631: Malicious code in voluntary_harrier_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'voluntary_harrier_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 through automated publishing scripts, which can lead to a polluted registry and potential security risks for users.

Vulnerability Detail

The vulnerability in 'voluntary_harrier_dumbs' stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes these variants, which can lead to the pollution of the npm registry. This not only affects the integrity of the registry but also poses risks to developers who may unknowingly use these compromised packages, potentially introducing security flaws into their applications.

How To Fix

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

npm uninstall voluntary_harrier_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 workaround, you can avoid using the 'voluntary_harrier_dumbs' package altogether. If it is already part of your project, consider removing it and replacing it with a trusted alternative. You can also monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring access to your code or installation.

Conclusion

The 'voluntary_harrier_dumbs' package poses a significant risk due to its malicious nature and the potential for security vulnerabilities in applications that use it. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their software.

See every vulnerability recorded for voluntary_harrier_dumbs →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.

Using this package can lead to the introduction of security flaws and pollution of the npm registry, affecting the integrity of your application.

You should remove the 'voluntary_harrier_dumbs' package from your project and monitor for any updates or patches.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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