Malicious Code Injection in binding_grouse_dumbs: A Threat to npm Packages
Summary
MAL-2025-99977: Malicious code in binding_grouse_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 package 'binding_grouse_dumbs' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These malicious packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues within the npm ecosystem.
Vulnerability Detail
The vulnerability in 'binding_grouse_dumbs' originates from its association with the tea.xyz token reward campaign. The package contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional code execution and dependency issues for developers who may unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall binding_grouse_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 avoid using the 'binding_grouse_dumbs' package altogether. If it is already in your project, remove it by executing: npm uninstall binding_grouse_dumbs. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The 'binding_grouse_dumbs' package poses a significant security risk due to its malicious code designed to manipulate npm registry data. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert. Regular updates and vigilance are essential to maintaining a secure development environment.
See every vulnerability recorded for binding_grouse_dumbs →
FAQ
The vulnerability involves malicious scripts that modify package metadata and flood the npm registry with derivative packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using the command: npm uninstall binding_grouse_dumbs.
Currently, there is no patched version available. It is best to remove the package until a secure version is released.
Keeping this package can lead to security vulnerabilities, unintentional code execution, and dependency issues, potentially compromising your application.
