Malicious Code Injection in mild_flamingo_0xrequest: A Threat to npm Packages

mild_flamingo_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105837: Malicious code in mild_flamingo_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mild_flamingo_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in mild_flamingo_0xrequest stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to reputation damage and security breaches.

How To Fix

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

npm uninstall mild_flamingo_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 avoid using the mild_flamingo_0xrequest package altogether. If it is a dependency of another package, consider removing that package or replacing it with a more reputable alternative.

Conclusion

The mild_flamingo_0xrequest package poses significant risks due to its malicious nature, which can compromise the integrity of the npm registry and affect developers using it. It is essential to take proactive measures to remove such packages and monitor for vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for mild_flamingo_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

Using compromised packages can lead to security breaches, reputation damage, and potential data loss or corruption.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about security advisories related to the packages you use.

Remove the package immediately and replace it with a secure alternative. Review your project's dependencies for any other potential vulnerabilities.

How To Fix

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

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