Malicious Code Injection in critical_chipmunk_dumbs Package
Summary
MAL-2025-101078: Malicious code in critical_chipmunk_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 critical_chipmunk_dumbs package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores. This package is particularly vulnerable due to its inclusion of autopublish scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the critical_chipmunk_dumbs package, 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 compromising the integrity of other packages. The malicious payload can affect developers by inflating reputation scores through deceptive practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall critical_chipmunk_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 installation of this package by using npm's package-lock.json to lock down your dependencies. Additionally, consider using the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The critical_chipmunk_dumbs package poses a significant risk due to its malicious code that alters package metadata and republishing behavior. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their software.
See every vulnerability recorded for critical_chipmunk_dumbs →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should remove the critical_chipmunk_dumbs package from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
