Malicious Code Injection in internal_chickadee_0xrequest Package

internal_chickadee_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104351: Malicious code in internal_chickadee_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The internal_chickadee_0xrequest package is part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate requests within applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, which can compromise application integrity and security.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the internal_chickadee_0xrequest package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores for token rewards, leading to potential pollution of the npm registry and exploitation of applications that depend on this package. The ramifications include unauthorized access to sensitive data, application instability, and a compromised development environment.

How To Fix

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

npm uninstall internal_chickadee_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, consider removing the internal_chickadee_0xrequest package from your project until a secure version is available. You can do this by executing: npm uninstall internal_chickadee_0xrequest. Additionally, review your package-lock.json file for any other potentially affected packages.

Conclusion

The internal_chickadee_0xrequest package has been identified as containing malicious code that poses significant risks to applications relying on it. It is crucial to take immediate action by updating or removing the package to safeguard your application from potential exploitation.

See every vulnerability recorded for internal_chickadee_0xrequest →

Share this vulnerability

FAQ

It is an npm package used for making requests within JavaScript applications, but it has been compromised with malicious code.

The vulnerability can lead to unauthorized modifications in your application, potentially exposing sensitive data and compromising application integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.

As a temporary measure, you can uninstall the package and review your dependencies for any other vulnerabilities.

Detailed information can be found in the vulnerability report on the official npm registry or through security advisories related to the package.

How To Fix

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

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