Malicious Code Injection in serious_fly_0xrequest Package

serious_fly_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108558: Malicious code in serious_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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The serious_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 various functionalities related to token rewards but has been compromised. It is known for its ability to create and publish derivative packages automatically, which can lead to reputation inflation for developers involved in the tea protocol.

Vulnerability Detail

The vulnerability in the serious_fly_0xrequest package stems from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The malicious payload is part of a broader scheme to inflate developer reputation scores through the automatic generation and publication of numerous derivative packages, potentially compromising the integrity of the npm ecosystem.

How To Fix

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

npm uninstall serious_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 remove the serious_fly_0xrequest package from your project by executing the following command: npm uninstall serious_fly_0xrequest. This will prevent the execution of any malicious code associated with the package until a fix is applied.

Conclusion

The serious_fly_0xrequest package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is essential for developers to take immediate action by updating or removing the package to safeguard their projects from potential threats.

See every vulnerability recorded for serious_fly_0xrequest →

Share this vulnerability

FAQ

The serious_fly_0xrequest package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project and potentially affecting its reputation and security.

If you are using the serious_fly_0xrequest package, you should update it to the latest patched version or remove it from your project to avoid security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

More information can be found in the vulnerability details provided by sources like Amazon Inspector and the official npm registry.

How To Fix

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

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