Malicious Code Exploit in tense_damselfly_0xrequest Package
Summary
MAL-2025-109548: Malicious code in tense_damselfly_0xrequest (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 tense_damselfly_0xrequest package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate package metadata and publish numerous derivative packages, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It contains scripts that automatically 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 and can inflate developer reputation scores fraudulently. The malicious payload poses significant risks, including the potential for dependency confusion and the introduction of further vulnerabilities into projects that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tense_damselfly_0xrequestIf 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 workaround, you can temporarily avoid using the tense_damselfly_0xrequest package by removing it from your dependencies. You can do this by running the command: npm uninstall tense_damselfly_0xrequest. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The tense_damselfly_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your dependencies and monitor your applications for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for tense_damselfly_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and publish harmful derivatives.
The vulnerability can lead to the pollution of the npm registry, potentially introducing further vulnerabilities into your application and compromising its integrity.
You should uninstall the tense_damselfly_0xrequest package immediately and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
