Malicious Code Injection in ajmalrashid Package: A Threat to npm Ecosystem
Summary
MAL-2025-170755: Malicious code in ajmalrashid (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 ajmalrashid 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 distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the ajmalrashid package originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically generate and publish derivative packages with randomized names, designed to inflate developer reputation scores. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby polluting the npm registry and potentially compromising other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ajmalrashidIf 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 prevent the installation of the ajmalrashid package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include ajmalrashid in its dependencies. You can check for vulnerabilities using Vulert, which allows you to monitor your package-lock.json for real-time alerts on open-source vulnerabilities.
Conclusion
The ajmalrashid package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for ajmalrashid →
FAQ
The ajmalrashid package is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
If your project includes the ajmalrashid package, it may be at risk of being compromised due to the malicious scripts that modify package.json and republish variants.
You should uninstall the ajmalrashid package immediately to mitigate any potential risks associated with its malicious behavior.
You can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to access the code or install additional tools.
Regularly audit your dependencies and use tools like Vulert to stay informed about vulnerabilities in your project's dependencies.
