Malicious Code Vulnerability in sure_damselfly_requirement Package
Summary
MAL-2025-96885: Malicious code in sure_damselfly_requirement (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 sure_damselfly_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to various malicious activities in the npm registry. The package is designed to facilitate the automatic generation and publication of derivative packages, which can lead to reputation inflation for developers involved in the campaign.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the sure_damselfly_requirement package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, often themed around Indonesian culture. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. Developers using this package may unknowingly contribute to the proliferation of malicious content in the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sure_damselfly_requirementIf 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 sure_damselfly_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file does not include any references to this package.
Conclusion
The sure_damselfly_requirement package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial for developers to remove this package from their projects and monitor for any potential vulnerabilities using tools like Vulert.
See every vulnerability recorded for sure_damselfly_requirement →
FAQ
The sure_damselfly_requirement package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
Using the sure_damselfly_requirement package can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the sure_damselfly_requirement package immediately and check your project for any unintended consequences caused by its use.
Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Vulert uses package-lock.json to provide real-time alerts without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
