Malicious Code Injection in capable_flamingo-silentdev Package
Summary
MAL-2025-100255: Malicious code in capable_flamingo-silentdev (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 capable_flamingo-silentdev package is part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate certain functionalities within these applications. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for legitimate packages to be found. The malicious payload can lead to unauthorized access, data breaches, and the potential for further exploitation within affected applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall capable_flamingo-silentdevIf 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your package-lock.json file is up-to-date and does not include the capable_flamingo-silentdev package. You can also use Vulert to monitor your dependencies for vulnerabilities without requiring code access. Visit https://vulert.com/scanner to check if your application is affected by this vulnerability.
Conclusion
The capable_flamingo-silentdev package poses a significant security risk due to its malicious code that modifies package.json files and inflates developer reputation scores. It is essential to take immediate action by uninstalling the package and monitoring your application for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for capable_flamingo-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign, designed to exploit npm's publishing mechanisms.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your application to further security risks.
You should uninstall the capable_flamingo-silentdev package immediately and monitor your dependencies for any further vulnerabilities.
Yes, you can use Vulert to monitor your application for vulnerabilities in real-time. Visit Vulert Scanner for more information.
Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities.
