Malicious Code Injection in panicky_damselfly_dumbs Package
Summary
MAL-2025-106891: Malicious code in panicky_damselfly_dumbs (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 panicky_damselfly_dumbs 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. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the panicky_damselfly_dumbs package, which is part of a broader scheme to manipulate the npm registry. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks 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 panicky_damselfly_dumbsIf 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 panicky_damselfly_dumbs package and any other packages that may be part of the same malicious campaign. Consider using alternative packages that provide similar functionalities but are verified and trusted. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time without requiring access to your code.
Conclusion
The panicky_damselfly_dumbs package presents a significant security risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for panicky_damselfly_dumbs →
FAQ
It is an npm package identified as part of a malicious campaign that floods the npm registry with derivative packages to inflate developer reputation scores.
Using the panicky_damselfly_dumbs package can compromise the integrity of your project and expose it to security risks due to the malicious code it contains.
You should immediately uninstall the panicky_damselfly_dumbs package from your project and check for any other compromised packages.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring access to your code.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
