Malicious Code Injection in mild_flamingo_0xrequest: A Threat to npm Packages
Summary
MAL-2025-105837: Malicious code in mild_flamingo_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
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 →
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.