Malicious Code Vulnerability in secondary_anglerfish_0xrequest Package
Summary
MAL-2025-108483: Malicious code in secondary_anglerfish_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 secondary_anglerfish_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages with randomized names. This vulnerability poses a significant risk to developers and users who may unknowingly incorporate this package into their projects.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The malicious code within secondary_anglerfish_0xrequest modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk of unintentional code execution and dependency pollution for developers using this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall secondary_anglerfish_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 workaround, you can avoid using the secondary_anglerfish_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can utilize tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.
Conclusion
The secondary_anglerfish_0xrequest package contains malicious code that poses significant risks to developers and their applications. It is crucial to remove this package and monitor for vulnerabilities using tools like Vulert to ensure the security of your projects.
See every vulnerability recorded for secondary_anglerfish_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to unintentional code execution and dependency pollution, compromising the integrity of your application.
You should uninstall the secondary_anglerfish_0xrequest package immediately using 'npm uninstall secondary_anglerfish_0xrequest'.
No patches are available for this specific package; it is recommended to remove it entirely.
You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without requiring access to the code or installation.
