Malicious Code Injection in continued_lemur-silentdev Package
Summary
MAL-2025-100936: Malicious code in continued_lemur-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 continued_lemur-silentdev package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability originates from the package's involvement in a token reward campaign that exploits npm's publishing capabilities. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry, potentially affecting other developers and projects relying on npm packages. The malicious payload can compromise the integrity of the development environment and lead to unintentional usage of compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall continued_lemur-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 continued_lemur-silentdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall continued_lemur-silentdev.
Conclusion
The continued_lemur-silentdev package poses a significant risk due to its malicious behavior aimed at manipulating npm's publishing system. It is crucial for developers to remove this package and monitor their projects for any signs of compromise. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for continued_lemur-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your project, compromising its integrity and security.
You should uninstall the continued_lemur-silentdev package immediately and monitor your project for any unusual behavior.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
