Malicious Code Vulnerability in baqirrehman Package
Summary
MAL-2025-170950: Malicious code in baqirrehman (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 baqirrehman 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 npm's publishing system. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in the baqirrehman package originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the integrity of the packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall baqirrehmanIf 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 baqirrehman package and monitor your project for any dependencies that may have inadvertently included it. Use the following command to check for vulnerabilities in your project: npm audit.
Conclusion
The baqirrehman package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying vigilant and regularly updating dependencies can help maintain the security of your applications.
See every vulnerability recorded for baqirrehman →
FAQ
The baqirrehman package is an npm package identified as part of a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.
This vulnerability can compromise the integrity of your project by introducing malicious code and potentially leading to security breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed baqirrehman, you should uninstall it immediately using the command: npm uninstall baqirrehman.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities using just your package-lock.json file.
