Malicious Code Injection in potential_damselfly-silentdev Package
Summary
MAL-2025-107166: Malicious code in potential_damselfly-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 potential_damselfly-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 aimed at inflating developer reputation scores through the tea.xyz token reward system. This package is particularly vulnerable due to its inclusion in a series of autopublishing scripts that can compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious design of the potential_damselfly-silentdev package, which is linked to a broader campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall potential_damselfly-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 measure, you can avoid using the potential_damselfly-silentdev package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert to receive real-time alerts for any vulnerabilities.
Conclusion
The potential_damselfly-silentdev package poses a significant risk due to its malicious design aimed at manipulating the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the security of their applications.
See every vulnerability recorded for potential_damselfly-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
Using this package can lead to security breaches, as it modifies your package.json and may introduce other malicious behaviors.
You should remove the package from your project and monitor for any updates or patches that may be released.
Yes, Vulert allows you to monitor your package-lock.json for vulnerabilities without requiring code access or installation.
Regularly audit your dependencies, use tools like Vulert, and stay informed about the packages you include in your projects.
