Malicious Code Injection in dreadful_fly_0xrequest Package

dreadful_fly_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101767: Malicious code in dreadful_fly_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 dreadful_fly_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been compromised to include malicious scripts that can alter package metadata and republish variants, leading to potential abuse and pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the dreadful_fly_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the proliferation of unauthorized and potentially harmful packages in the npm registry. The ramifications include a compromised npm ecosystem, potential security risks for developers using these packages, and damage to the reputation of legitimate packages.

How To Fix

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

npm uninstall dreadful_fly_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 dreadful_fly_0xrequest package by using the npm shrinkwrap feature or by specifying exact versions of your dependencies in your package.json file to avoid pulling in this malicious package.

Conclusion

The dreadful_fly_0xrequest package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is crucial for developers to take immediate action to remove this package and implement monitoring solutions to safeguard their projects against similar vulnerabilities in the future.

See every vulnerability recorded for dreadful_fly_0xrequest →

Share this vulnerability

FAQ

The dreadful_fly_0xrequest 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.

This vulnerability can lead to unauthorized modifications of your package metadata, potential security risks, and the pollution of the npm registry with malicious packages.

You should remove the dreadful_fly_0xrequest package from your project immediately and monitor for any updates or patches that may address this vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software. You can also check your application against known vulnerabilities using the Vulert playground.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about vulnerabilities in the npm ecosystem to mitigate risks.

How To Fix

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

npm uninstall dreadful_fly_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