Malicious Code Injection in bright_gerbil_0xrequest Package
Summary
MAL-2025-100104: Malicious code in bright_gerbil_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 bright_gerbil_0xrequest package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to artificially inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and security of the npm ecosystem.
Vulnerability Detail
The vulnerability in the bright_gerbil_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This not only compromises the security of applications relying on this package but also pollutes the npm ecosystem, making it difficult for developers to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bright_gerbil_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 bright_gerbil_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your open-source packages.
Conclusion
The bright_gerbil_0xrequest package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert. Staying vigilant can help maintain the integrity of your applications and the broader npm ecosystem.
See every vulnerability recorded for bright_gerbil_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the bright_gerbil_0xrequest package immediately and check your package-lock.json for any references to it.
Yes, tools like Vulert can monitor your open-source dependencies in real-time for vulnerabilities without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
