Malicious Code Injection in hollow_boar_requirement Package

hollow_boar_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94837: Malicious code in hollow_boar_requirement (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 hollow_boar_requirement package is part of the npm ecosystem, commonly used for managing dependencies in JavaScript applications. This package has been identified as part of a broader malicious campaign targeting npm, where packages are designed to inflate developer reputation scores through automated publishing of derivative packages. The hollow_boar_requirement package specifically contains scripts that modify its own metadata and continuously republish variants, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the hollow_boar_requirement package, which includes malicious scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names and republish itself, potentially leading to the proliferation of harmful packages in the npm registry. The ramifications include compromised developer environments, increased risk of dependency confusion attacks, and a polluted package ecosystem that can affect other developers and applications relying on npm.

How To Fix

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

npm uninstall hollow_boar_requirement

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 measure, you can avoid using the hollow_boar_requirement package and any other packages that may have been published as part of this malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and remove any potentially harmful packages.

Conclusion

The hollow_boar_requirement package poses a significant risk due to its malicious code that alters package metadata and republish behavior. It is crucial for developers to remove this package from their projects and utilize tools to monitor for vulnerabilities. Staying informed and proactive can help maintain a secure development environment.

See every vulnerability recorded for hollow_boar_requirement →

Share this vulnerability

FAQ

The hollow_boar_requirement package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by automatically publishing derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially introducing harmful packages into your application and compromising your development environment.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If you find the hollow_boar_requirement package in your project, uninstall it immediately using 'npm uninstall hollow_boar_requirement' and audit your dependencies.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your dependencies effectively.

How To Fix

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

npm uninstall hollow_boar_requirement

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