Malicious Code Injection in gopalsharma Package: npm Vulnerability Overview
Summary
MAL-2025-171271: Malicious code in gopalsharma (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The gopalsharma package is part of the npm ecosystem, primarily used for JavaScript development. It has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the gopalsharma package, which contains malicious code that 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, effectively polluting the npm registry. The ramifications include potential security risks for developers who may unknowingly use these compromised packages, as well as the degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gopalsharmaIf 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 gopalsharma package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The gopalsharma package poses a significant threat due to its malicious code that manipulates the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like npm audit and Vulert can help maintain the security of your projects.
See every vulnerability recorded for gopalsharma →
FAQ
The gopalsharma package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and pollution of the npm registry.
You should uninstall the gopalsharma package immediately using 'npm uninstall gopalsharma' and monitor your project for any other vulnerabilities.
You can use tools like npm audit to check for vulnerabilities in your dependencies. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
