Malicious Code Injection in unemployed_silverfish-biggestdev Package
Summary
MAL-2025-110081: Malicious code in unemployed_silverfish-biggestdev (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 unemployed_silverfish-biggestdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability in the unemployed_silverfish-biggestdev package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of untrustworthy packages in the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unemployed_silverfish-biggestdevIf 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 unemployed_silverfish-biggestdev package altogether. If it is already included in your project, consider removing it from your package.json file and running npm uninstall unemployed_silverfish-biggestdev to eliminate any potential risks associated with it.
Conclusion
The unemployed_silverfish-biggestdev package poses a significant risk due to its malicious behavior of modifying package files and proliferating untrustworthy packages. It is crucial for developers to be vigilant and take necessary actions to mitigate the risks associated with this vulnerability.
See every vulnerability recorded for unemployed_silverfish-biggestdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the inclusion of untrustworthy packages in your application, which may compromise security and stability.
You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
