Malicious Code Injection in balvindersingh Package: A Threat to npm Users
Summary
MAL-2025-170949: Malicious code in balvindersingh (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 balvindersingh package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, potentially affecting developers and users who rely on its functionality.
Vulnerability Detail
The vulnerability in the balvindersingh package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts designed to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, thereby polluting the npm registry. The ramifications include inflated developer reputation scores and the risk of users unknowingly installing compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall balvindersinghIf 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, avoid using the balvindersingh package and monitor your project for any dependencies that may have been affected by this malicious code. Regularly check your package-lock.json file for any unauthorized changes.
Conclusion
The balvindersingh package poses a significant risk due to its malicious code designed to exploit npm's publishing system. It is essential for developers to remain vigilant, uninstall any affected packages, and utilize tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for balvindersingh →
FAQ
The balvindersingh 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 installation of malicious packages, which may compromise your project's integrity and security.
You should uninstall the balvindersingh package immediately and check your project for any unauthorized changes.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
