Malicious Code Vulnerability in ugliest_firefly_0xrequest Package

ugliest_firefly_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109949: Malicious code in ugliest_firefly_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ugliest_firefly_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for token rewards in the tea.xyz protocol. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in the ugliest_firefly_0xrequest package originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of other packages. This can lead to security risks, including the installation of malicious code by unsuspecting developers.

How To Fix

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

npm uninstall ugliest_firefly_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 workaround, avoid using the ugliest_firefly_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. Always review the packages you include in your project for any known vulnerabilities.

Conclusion

The ugliest_firefly_0xrequest package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any identified vulnerabilities. Regular monitoring and updating of dependencies can help maintain the security of your projects.

See every vulnerability recorded for ugliest_firefly_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of malicious code, compromising the security of your project and potentially affecting other dependencies.

You should uninstall the ugliest_firefly_0xrequest package immediately and review your project for any other potentially malicious packages.

You can use tools like 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 if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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