Malicious Code Injection in dramatic_flyingfish_0xrequest Package
Summary
MAL-2025-101758: Malicious code in dramatic_flyingfish_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The dramatic_flyingfish_0xrequest package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package is associated with the tea.xyz token reward scheme, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the dramatic_flyingfish_0xrequest package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The origin of this issue is linked to a broader campaign that leverages npm for malicious purposes, specifically targeting developers involved in the tea protocol token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dramatic_flyingfish_0xrequestIf 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 dramatic_flyingfish_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The dramatic_flyingfish_0xrequest package poses a significant security risk due to its malicious code that alters package configurations and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities.
See every vulnerability recorded for dramatic_flyingfish_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The malicious code can modify your package.json file, leading to potential security risks and the pollution of your application's dependencies.
You should uninstall the package immediately and check for any dependencies that may rely on it.
Yes, tools like Vulert can monitor your package-lock.json file for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
