Malicious Code Injection in yabbering_weasel_dumbs Package
Summary
MAL-2025-111150: Malicious code in yabbering_weasel_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 'yabbering_weasel_dumbs' package is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to facilitate automatic publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability in the 'yabbering_weasel_dumbs' package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk of reputation damage to developers and potential exploitation of their projects. The package's design allows it to continuously republish variants, making it difficult to track and mitigate the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall yabbering_weasel_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 prevent the package from being used in your project by removing it from your package.json file and locking the version of your dependencies to avoid automatic updates that may include this malicious package.
Conclusion
The 'yabbering_weasel_dumbs' package poses a significant security risk due to its malicious code that modifies project files and repopulates the npm registry with compromised packages. Immediate action is required to remove this package and safeguard your project from potential exploitation.
See every vulnerability recorded for yabbering_weasel_dumbs →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automatic publishing of derivative packages.
The vulnerability can lead to reputation damage, pollution of the npm registry, and potential exploitation of your project through the introduction of malicious code.
You should immediately uninstall the package using 'npm uninstall yabbering_weasel_dumbs' and check your project for any dependencies that may be affected.
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 check your application for vulnerabilities without requiring access to the code or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
