Malicious Code Injection in fragile_anglerfish_0xrequest Package

fragile_anglerfish_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102888: Malicious code in fragile_anglerfish_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 fragile_anglerfish_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 are often used to inflate developer reputation scores for token rewards. However, its functionality has been compromised, making it vulnerable to exploitation.

Vulnerability Detail

The vulnerability in the fragile_anglerfish_0xrequest package stems from its malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, posing a risk to developers who may unknowingly use these compromised packages. The origin of this vulnerability is linked to the package's involvement in a broader scheme aimed at manipulating the npm ecosystem for token rewards.

How To Fix

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

npm uninstall fragile_anglerfish_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 avoid using the fragile_anglerfish_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The fragile_anglerfish_0xrequest package poses a significant risk due to its malicious code that alters project files and repopulates the npm registry with compromised packages. It is essential to remove this package and monitor your projects for any vulnerabilities to maintain security.

See every vulnerability recorded for fragile_anglerfish_0xrequest →

Share this vulnerability

FAQ

It is an npm package that was part of a token reward campaign but has been found to contain malicious code.

The vulnerability can lead to the modification of your package.json file and the introduction of unwanted packages, potentially compromising your project's integrity.

You should uninstall the fragile_anglerfish_0xrequest package immediately and check for any unauthorized changes in your project.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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