Malicious Code Injection in radical_chipmunk-notthedev Package
Summary
MAL-2025-107690: Malicious code in radical_chipmunk-notthedev (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 radical_chipmunk-notthedev package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability stems from the package's malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can compromise the integrity of the npm ecosystem and lead to potential exploitation of developers who unknowingly use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall radical_chipmunk-notthedevIf 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 remove the radical_chipmunk-notthedev package from your project by executing: 'npm uninstall radical_chipmunk-notthedev'. This will prevent any malicious code from executing while you assess your project's dependencies.
Conclusion
The radical_chipmunk-notthedev package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be aware of this vulnerability, take necessary actions to remove the package, and utilize tools like Vulert for ongoing monitoring of their dependencies.
See every vulnerability recorded for radical_chipmunk-notthedev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately and check your project for any other potentially malicious dependencies.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
