Malicious Code Injection in written_parrotfish_0xrequest Package
Summary
MAL-2025-111038: Malicious code in written_parrotfish_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 written_parrotfish_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages. The primary functionality of this package is overshadowed by its malicious intent, which includes modifying package metadata and inflating developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in the written_parrotfish_0xrequest package stems from its association with the tea.xyz token reward campaign. This package contains scripts designed to automatically publish derivative packages with altered metadata, including the removal of private flags and the generation of random package names. The malicious payload can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising the integrity of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall written_parrotfish_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 monitor your package dependencies using tools like Vulert. By utilizing Vulert, you can check if your application is affected by this vulnerability without requiring code access or installation. You can use the Vulert playground at https://vulert.com/scanner to analyze your package-lock.json file for vulnerabilities.
Conclusion
The written_parrotfish_0xrequest package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and regularly audit their dependencies to prevent such vulnerabilities from affecting their applications.
See every vulnerability recorded for written_parrotfish_0xrequest →
FAQ
The written_parrotfish_0xrequest package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of applications that depend on the affected package.
You should uninstall the written_parrotfish_0xrequest package immediately and check your project for any other potentially malicious packages.
You can use tools like Vulert to monitor your package dependencies in real-time for open-source vulnerabilities.
There is no patch for the written_parrotfish_0xrequest package; the recommended action is to uninstall it and avoid using similar packages.
