Malicious Code Injection in heavy_bobolink_dumbs Package
Summary
MAL-2025-103629: Malicious code in heavy_bobolink_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 heavy_bobolink_dumbs package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the heavy_bobolink_dumbs package, which includes autopublish scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. The malicious payload can affect developers' reputations and the overall trustworthiness of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall heavy_bobolink_dumbs
If 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 heavy_bobolink_dumbs package and any packages that depend on it. Additionally, consider using a tool like Vulert to monitor your package-lock.json file for vulnerabilities in real-time. 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 heavy_bobolink_dumbs package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for heavy_bobolink_dumbs →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should uninstall the heavy_bobolink_dumbs package immediately and check for any dependencies that may rely on it.
Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.