Malicious Code Injection in structural_damselfly_0xrequest Package
Summary
MAL-2025-109211: Malicious code in structural_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 structural_damselfly_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation and publication of derivative packages. This package is particularly vulnerable due to its association with autopublish scripts that can modify its own metadata and behavior.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign linked to 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 numerous derivative packages with random names. This behavior can lead to pollution of the npm registry and potentially compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall structural_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 temporary workaround, you can avoid using the structural_damselfly_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The structural_damselfly_0xrequest package has been identified as malicious, capable of altering its own metadata and creating derivative packages that can compromise application integrity. It is crucial to remove this package and monitor your project for vulnerabilities using tools like Vulert.
See every vulnerability recorded for structural_damselfly_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the modification of your package's metadata and the creation of numerous unwanted derivative packages, potentially compromising your application's integrity.
You should remove the structural_damselfly_0xrequest package from your project and look for alternatives.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. It requires only the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
