Malicious Code Vulnerability in individual_worm-silentdev Package
Summary
MAL-2025-104166: Malicious code in individual_worm-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 individual_worm-silentdev 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 generation of derivative packages. It is designed to automatically publish variants with altered metadata, making it susceptible to exploitation.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the individual_worm-silentdev package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall individual_worm-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 remove the individual_worm-silentdev package from your project by executing the following command: npm uninstall individual_worm-silentdev. This will prevent any malicious code from executing while you seek a more permanent solution.
Conclusion
The individual_worm-silentdev package contains malicious code that poses a significant risk to developers and their projects. It is crucial to take immediate action by updating or removing the package to mitigate potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities in your open-source dependencies.
See every vulnerability recorded for individual_worm-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project relies on compromised packages.
You should uninstall the individual_worm-silentdev package immediately and check for any updates or patches for your dependencies.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
