Malicious Code Injection in devkishore Package: A Threat to npm Ecosystem
Summary
MAL-2025-171107: Malicious code in devkishore (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 devkishore package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate various functionalities within applications. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with harmful scripts.
Vulnerability Detail
The vulnerability in the devkishore package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially leading to security risks for users who unknowingly install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall devkishore
If 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 measure, avoid using the devkishore package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure they are secure.
Conclusion
The devkishore package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and to stay vigilant about the security of their dependencies. Utilizing tools like Vulert can aid in monitoring for vulnerabilities effectively.
See every vulnerability recorded for devkishore →
FAQ
The devkishore package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
If your application uses the devkishore package, it may be at risk of installing malicious scripts that can compromise your application's integrity and security.
You should uninstall the devkishore package immediately using 'npm uninstall devkishore' and audit your project for any other potentially malicious packages.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies using tools like npm audit, and keep your packages updated to their latest versions to mitigate security risks.