Malicious Code Injection in deliberate_junglefowl-silentdev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101294: Malicious code in deliberate_junglefowl-silentdev (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 deliberate_junglefowl-silentdev package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages are designed to inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the deliberate_junglefowl-silentdev package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall deliberate_junglefowl-silentdev

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 deliberate_junglefowl-silentdev package altogether. Instead, consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.

Conclusion

The deliberate_junglefowl-silentdev package poses significant risks due to its malicious code that alters package configurations and pollutes the npm registry. It is essential to remove this package and monitor your applications for vulnerabilities to maintain security.

See every vulnerability recorded for deliberate_junglefowl-silentdev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code that affects the npm registry.

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

You should uninstall the package immediately using 'npm uninstall deliberate_junglefowl-silentdev' and check for any dependencies that may be affected.

Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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 deliberate_junglefowl-silentdev

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