Malicious Code Injection in independent_junglefowl-strongdev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104151: Malicious code in independent_junglefowl-strongdev (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 independent_junglefowl-strongdev package is part of the npm ecosystem, which is widely used for JavaScript development. This package was associated with a token reward campaign that aimed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises its integrity and poses risks to developers using it.

Vulnerability Detail

The vulnerability stems from the package's malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can affect developers' projects by introducing untrusted code. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploited npm's publishing mechanisms.

How To Fix

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

npm uninstall independent_junglefowl-strongdev

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 avoid using the independent_junglefowl-strongdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can help identify vulnerabilities in your package-lock.json file.

Conclusion

The independent_junglefowl-strongdev package poses a significant risk due to its malicious code that alters project files and repopulates the npm registry with untrusted packages. It is crucial for developers to remove this package and monitor their dependencies to maintain the security of their projects.

See every vulnerability recorded for independent_junglefowl-strongdev →

Share this vulnerability

FAQ

It is an npm package that was part of a token reward campaign, designed to inflate developer reputation scores through automated package publishing.

The vulnerability can introduce malicious code into your project, potentially compromising its security and integrity.

You should uninstall the package immediately and check for any alternative packages that can fulfill your requirements.

You can use Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities without needing to install any additional software.

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 independent_junglefowl-strongdev

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