Malicious Code Injection in rising_damselfly_0xrequest Package

rising_damselfly_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108157: Malicious code in rising_damselfly_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The rising_damselfly_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. However, this package has been identified as containing malicious code that compromises its integrity and the security of applications relying on it.

Vulnerability Detail

The vulnerability in the rising_damselfly_0xrequest package stems from its inclusion in a campaign that floods the npm registry with malicious packages. This package modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry. The malicious payload can lead to unauthorized access and manipulation of project dependencies, potentially allowing attackers to exploit affected applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rising_damselfly_0xrequest

If 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 prevent the installation of the rising_damselfly_0xrequest package by using the following command to uninstall it: npm uninstall rising_damselfly_0xrequest. Additionally, consider using a package-lock.json file to lock down your dependencies and avoid unintentional updates to malicious packages.

Conclusion

The rising_damselfly_0xrequest package poses a significant security risk due to its malicious code. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for rising_damselfly_0xrequest →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign and is designed to generate and publish derivative packages.

The malicious code can modify your package.json file, remove private flags, and introduce unauthorized packages, potentially compromising your application's security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

You should uninstall the rising_damselfly_0xrequest package immediately and monitor your application for any unusual behavior.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and keep your packages updated to mitigate risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rising_damselfly_0xrequest

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback