Malicious Code Injection in double_hare_requirement Package

double_hare_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94098: Malicious code in double_hare_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 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 double_hare_requirement package is part of the npm ecosystem, commonly used in JavaScript applications for managing dependencies. This package has been identified as part of a larger malicious campaign that aims to exploit npm's package management system. The vulnerability stems from the package's involvement in generating and publishing derivative packages with altered metadata, which can lead to reputation inflation and registry pollution.

Vulnerability Detail

The vulnerability in the double_hare_requirement package is characterized by the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. The origin of this vulnerability is linked to a campaign that floods npm with derivative packages, undermining the integrity of the ecosystem. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as a degradation of the npm registry's reliability.

How To Fix

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

npm uninstall double_hare_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 workaround, you can remove the double_hare_requirement package from your project by executing 'npm uninstall double_hare_requirement'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The double_hare_requirement package has been identified as a vector for malicious code injection, posing significant risks to developers and the integrity of the npm ecosystem. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.

See every vulnerability recorded for double_hare_requirement →

Share this vulnerability

FAQ

The double_hare_requirement package is an npm package used for managing dependencies in JavaScript applications, but it has been compromised with malicious code.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry.

If you have installed the double_hare_requirement package, it is crucial to uninstall it immediately and monitor for any updates or patches.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

To prevent similar vulnerabilities, regularly update your dependencies, use tools like Vulert for monitoring, and audit your package-lock.json file for any suspicious packages.

How To Fix

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

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