Malicious Code Injection in bikashagarwal Package: npm Vulnerability Overview
Summary
MAL-2025-170974: Malicious code in bikashagarwal (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 bikashagarwal 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 publishing numerous derivative packages with altered metadata. The primary function of this package is to facilitate the tea.xyz token reward campaign, which incentivizes developers to inflate their reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability originates from the bikashagarwal package being associated with a malicious campaign 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, which pollutes the npm registry and can potentially compromise the integrity of the software supply chain. The malicious payload can affect developers by misleading them into using compromised packages, thus exposing their applications to security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bikashagarwalIf 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 bikashagarwal package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The bikashagarwal package poses a significant security risk due to its association with a malicious campaign that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for bikashagarwal →
FAQ
The bikashagarwal package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
The vulnerability can lead to the inclusion of compromised packages in your application, potentially exposing it to security risks and affecting its integrity.
You should uninstall the bikashagarwal package immediately using 'npm uninstall bikashagarwal' and monitor your project for any further vulnerabilities.
Yes, you can use tools like Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground.
If you discover other malicious packages, remove them from your project and report them to the npm registry to help protect the community.
