Malicious Code Injection in amjadsameer Package: A Threat to npm Users
Summary
MAL-2025-170869: Malicious code in amjadsameer (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 amjadsameer 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 sharing of code among developers. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for users.
Vulnerability Detail
The vulnerability in the amjadsameer package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts designed to automatically publish derivative packages with altered metadata. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to the pollution of the npm registry and potential exploitation by attackers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall amjadsameerIf 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 amjadsameer package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The amjadsameer package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any affected packages. Regular monitoring and updates can help mitigate such vulnerabilities.
See every vulnerability recorded for amjadsameer →
FAQ
The amjadsameer package is a JavaScript package available on npm, but it has been identified as part of a malicious campaign that exploits npm's publishing features.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the amjadsameer package immediately using 'npm uninstall amjadsameer' and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, you should look for reputable packages that provide similar functionality and have a good track record in the community.
