Malicious Code Injection in printed_damselfly_0xrequest Package
Summary
MAL-2025-107279: Malicious code in printed_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 printed_damselfly_0xrequest package is part of the npm ecosystem, often used for various JavaScript applications. This package has been identified as part of a broader malicious campaign targeting npm, where packages are created to inflate developer reputation scores through automated scripts. The malicious nature of this package lies in its ability to alter package metadata and republish variants, thus polluting the npm registry.
Vulnerability Detail
The vulnerability in the printed_damselfly_0xrequest package originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the proliferation of malicious packages in the npm registry, potentially compromising the integrity of applications that depend on them. The ramifications include security risks for developers and users, as well as damage to the reputation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall printed_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 printed_damselfly_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The printed_damselfly_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is essential for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for printed_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 introduction of malicious code in your application, compromising its security and integrity.
You should uninstall the printed_damselfly_0xrequest package immediately and check for any alternative packages.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
