Malicious Code Vulnerability in Changing Baboon Dumbs Package
Summary
MAL-2025-100319: Malicious code in changing_baboon_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
Changing Baboon Dumbs is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the package's 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, polluting the npm registry and potentially affecting other packages and developers. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult for developers to identify and mitigate the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall changing_baboon_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 changing_baboon_dumbs package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The changing_baboon_dumbs package poses a significant security risk due to its malicious code that alters package configurations and pollutes the npm registry. It is essential to remove this package from your projects and monitor for any similar vulnerabilities in the future.
See every vulnerability recorded for changing_baboon_dumbs →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publishing of derivative packages.
The malicious code modifies your package.json, removes private flags, and continuously republishes variants, which can lead to pollution of the npm registry and potential security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the changing_baboon_dumbs package immediately using 'npm uninstall changing_baboon_dumbs' and look for alternative packages.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions to minimize security risks.
