Malicious Code Injection in broad_gibbon_dumbs Package
Summary
MAL-2025-100122: Malicious code in broad_gibbon_dumbs (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 broad_gibbon_dumbs package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in the broad_gibbon_dumbs package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes. The ramifications include potential exposure of applications to untrusted code and the degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall broad_gibbon_dumbsIf 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 remove the broad_gibbon_dumbs package from your project by executing the following command: npm uninstall broad_gibbon_dumbs. This will prevent any malicious code from executing in your application.
Conclusion
The broad_gibbon_dumbs package contains a significant vulnerability that can compromise the security of applications relying on it. It is crucial to take immediate action by updating or removing the package to safeguard your project. Utilizing tools like Vulert can help maintain the security of your dependencies.
See every vulnerability recorded for broad_gibbon_dumbs →
FAQ
The broad_gibbon_dumbs package is an npm package involved in the tea.xyz token reward campaign, which automates the creation and publication of derivative packages.
The vulnerability can lead to the execution of untrusted code in your application, potentially compromising its security and integrity.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.
If you cannot update the package, it is advisable to remove it from your project to mitigate the risk of malicious code execution.
Regularly audit your dependencies using tools like npm audit, and consider using services like Vulert to monitor for vulnerabilities in real-time.
