Malicious Code Injection in excessive_junglefowl_0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102330: Malicious code in excessive_junglefowl_0xrequest (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 excessive_junglefowl_0xrequest package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages designed to inflate developer reputation scores for token rewards. Its primary attributes include automatic publishing scripts that generate random package names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the excessive_junglefowl_0xrequest package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the continuous republishing of these variants. As a result, it compromises the integrity of the npm registry and can potentially affect applications that rely on this package, leading to security risks and reputation damage for developers.

How To Fix

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

npm uninstall excessive_junglefowl_0xrequest

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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include excessive_junglefowl_0xrequest in its dependencies.

Conclusion

The excessive_junglefowl_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor for any future vulnerabilities using tools like Vulert.

See every vulnerability recorded for excessive_junglefowl_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application if it relies on this package.

You should uninstall the package immediately using the command: npm uninstall excessive_junglefowl_0xrequest.

Currently, there is no patched version available for excessive_junglefowl_0xrequest. It is recommended to remove the package entirely.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.

How To Fix

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

npm uninstall excessive_junglefowl_0xrequest

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