Malicious Code Injection in specific_dragonfly-strongdev Package
Summary
MAL-2025-108988: Malicious code in specific_dragonfly-strongdev (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 specific_dragonfly-strongdev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the specific_dragonfly-strongdev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation by attackers. The origin of this issue is linked to a broader campaign that floods npm with similar malicious packages, making it a significant threat to developers and users relying on the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall specific_dragonfly-strongdevIf 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 specific_dragonfly-strongdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to package.json and revert them if necessary.
Conclusion
The specific_dragonfly-strongdev package poses a significant risk due to its embedded malicious code, which modifies critical files and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for specific_dragonfly-strongdev →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and compromising the integrity of your dependencies.
You should immediately remove the specific_dragonfly-strongdev package from your project and monitor your package.json for any unauthorized changes.
Yes, Vulert can help you monitor and alert in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
