Malicious Code Vulnerability in uneven_pheasant-silentdev Package
Summary
MAL-2025-110084: Malicious code in uneven_pheasant-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The uneven_pheasant-silentdev package is part of the npm ecosystem, typically used for various development purposes. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry. The package is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign.
Vulnerability Detail
This vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This can lead to significant issues, including the pollution of the npm registry and potential security risks for developers who inadvertently use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uneven_pheasant-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 avoid using the uneven_pheasant-silentdev package and monitor your project for any dependencies that may have been affected by this malicious code. Regularly check your package-lock.json file for any unauthorized changes.
Conclusion
The uneven_pheasant-silentdev package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is essential to remove this package from your project and monitor for any dependencies that may have been affected. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your software.
See every vulnerability recorded for uneven_pheasant-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project inadvertently uses compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without any signup.
You should uninstall the uneven_pheasant-silentdev package immediately and review your project for any dependencies that may have been affected.
There is no patch for the uneven_pheasant-silentdev package since it is recommended to remove it entirely from your project.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
