Malicious Code Injection in respectable_galliform_0xrequest Package
Summary
MAL-2025-107953: Malicious code in respectable_galliform_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 respectable_galliform_0xrequest package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This package is designed to automatically generate and publish derivative packages with randomized names, leading to potential abuse in the npm registry.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the respectable_galliform_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The malicious payload is part of a broader scheme that exploits npm's publishing capabilities, potentially affecting developers' reputations and the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall respectable_galliform_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 prevent the installation of the vulnerable package by using npm's package-lock.json to monitor dependencies. Additionally, you can use the following command to uninstall the package: npm uninstall respectable_galliform_0xrequest.
Conclusion
The respectable_galliform_0xrequest package contains malicious code that poses a significant risk to the npm ecosystem. It is crucial for developers to be aware of this vulnerability, take appropriate action to update or remove the package, and utilize tools like Vulert for ongoing monitoring.
See every vulnerability recorded for respectable_galliform_0xrequest →
FAQ
The malicious code can lead to the automatic generation of numerous derivative packages, which can clutter the npm registry and potentially harm developer reputations.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If a patched version is not available, it is advisable to remove the package from your project to mitigate the risk.
The payload modifies the package.json file, removes private flags, and continuously republishes variants with random names to pollute the npm registry.
Regularly auditing your dependencies and using tools like Vulert can help identify and mitigate vulnerabilities before they impact your projects.
