Malicious Code Injection in amjadhaseeb Package: npm Vulnerability Overview
Summary
MAL-2025-170842: Malicious code in amjadhaseeb (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 amjadhaseeb 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 floods the npm registry with harmful scripts. Its primary function is to manipulate package metadata and publish derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign.
Vulnerability Detail
The vulnerability in the amjadhaseeb package originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which can lead to the pollution of the npm registry. The potential ramifications include unauthorized access to sensitive information, increased risk of dependency confusion, and overall degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall amjadhaseebIf 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 remove the amjadhaseeb package from your project by executing: npm uninstall amjadhaseeb. Additionally, consider using a package-lock.json file to lock your dependencies and prevent the installation of malicious packages.
Conclusion
The amjadhaseeb package poses a significant risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications.
See every vulnerability recorded for amjadhaseeb →
FAQ
The amjadhaseeb package is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata and inflating developer reputation scores.
The vulnerability can lead to unauthorized modifications of your project's dependencies, potentially exposing sensitive information and compromising the integrity of your application.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you cannot update the package, consider removing it from your project and replacing it with a safer alternative. Additionally, review your package-lock.json file to ensure no malicious dependencies are included.
More information can be found in the vulnerability report on the GitHub repository for malicious packages or by consulting security advisories related to npm packages.
