Malicious Code Injection in eshankapoor Package - npm Vulnerability
Summary
MAL-2025-171170: Malicious code in eshankapoor (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 eshankapoor 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 continuously publish variants with altered metadata.
Vulnerability Detail
The vulnerability in the eshankapoor package originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can compromise the integrity of the packages within the ecosystem, potentially affecting developers who rely on these packages for their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eshankapoorIf 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 eshankapoor package and replace it with a trusted alternative. Always verify the integrity and source of any package before including it in your project.
Conclusion
The eshankapoor package poses a significant risk due to its malicious code designed to exploit the npm registry. It is essential to remove this package from your projects and to remain vigilant about the packages you use. Regular monitoring and updates can help safeguard your applications from similar vulnerabilities.
See every vulnerability recorded for eshankapoor →
FAQ
The eshankapoor package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application if it relies on affected packages.
You should uninstall the eshankapoor package immediately using 'npm uninstall eshankapoor' and review your dependencies for any other malicious packages.
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.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
