Malicious Code Injection in ajmalbashir Package: npm Vulnerability Alert
Summary
MAL-2025-170746: Malicious code in ajmalbashir (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 ajmalbashir package is part of the npm ecosystem, primarily used for JavaScript development. It has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the ajmalbashir package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ajmalbashirIf 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 ajmalbashir package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.
Conclusion
The ajmalbashir package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for ajmalbashir →
FAQ
The ajmalbashir package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the security of your application by introducing malicious code through derivative packages.
If you have installed ajmalbashir, you should uninstall it immediately using 'npm uninstall ajmalbashir' and check for any dependencies that may rely on it.
Currently, there is no patched version of the ajmalbashir package available. The best course of action is to remove the package from your project.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.
