Malicious Code Injection in vague_mockingbird_dumbs Package
Summary
MAL-2025-110313: Malicious code in vague_mockingbird_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 vague_mockingbird_dumbs 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 manipulate the npm registry by generating and publishing derivative packages with randomized names. The primary functionality of these packages is to inflate developer reputation scores for token rewards, but they also pose significant security risks due to their malicious payloads.
Vulnerability Detail
The vulnerability in the vague_mockingbird_dumbs package stems from its inclusion in a malicious campaign that 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, which pollutes the npm registry and can compromise the integrity of other packages. The origin of this vulnerability is linked to the automated scripts included in the package, which are designed to exploit the npm ecosystem for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vague_mockingbird_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 workaround, you can manually remove the vague_mockingbird_dumbs package from your project by executing the following command: npm uninstall vague_mockingbird_dumbs. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The vague_mockingbird_dumbs package poses a significant security risk due to its malicious code designed to exploit the npm ecosystem. It is crucial to remove this package from your project and monitor for any potential vulnerabilities using tools like Vulert.
See every vulnerability recorded for vague_mockingbird_dumbs →
FAQ
It is an npm package associated with a malicious campaign aimed at inflating developer reputation scores through automated publishing.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
Currently, there is no known patched version of the vague_mockingbird_dumbs package. The recommended action is to remove it from your project.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You should uninstall the vague_mockingbird_dumbs package immediately to mitigate the risk associated with this vulnerability.
