Malicious Code Injection in garimapandey Package: npm Vulnerability Overview
Summary
MAL-2025-171256: Malicious code in garimapandey (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 garimapandey 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 associated with the tea.xyz token reward initiative. Its primary function is to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, this functionality has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability in the garimapandey package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to pollute the npm registry by continuously republishing variants, which can lead to a loss of trust in the npm ecosystem and potential exploitation of developers who unknowingly use these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm registry with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall garimapandeyIf 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 garimapandey package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The garimapandey package poses a significant security risk due to its malicious code that alters project files and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for garimapandey →
FAQ
The garimapandey package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json file and floods the npm registry with unwanted packages.
You should immediately uninstall the garimapandey package using npm uninstall garimapandey and audit your project for any other potentially malicious dependencies.
Yes, you can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing 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.
