Malicious Code Injection in chandrakantgupta Package: npm Vulnerability Overview
Summary
MAL-2025-171020: Malicious code in chandrakantgupta (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 chandrakantgupta package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish numerous variants with random names.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the chandrakantgupta package, which is linked to the tea.xyz token reward campaign. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of these variants, effectively polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall chandrakantguptaIf 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 chandrakantgupta package from your project by executing: npm uninstall chandrakantgupta. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The chandrakantgupta package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the affected package, and utilize monitoring tools like Vulert to safeguard their applications.
See every vulnerability recorded for chandrakantgupta →
FAQ
The chandrakantgupta package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting your application's security.
If you have installed the chandrakantgupta package, it is advisable to uninstall it immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
