Malicious Code Injection in amjadsamra Package: A Threat to npm Ecosystem
Summary
MAL-2025-170872: Malicious code in amjadsamra (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 amjadsamra 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and the integrity of the registry itself.
Vulnerability Detail
The vulnerability in the amjadsamra package originates from its association with the tea.xyz token reward campaign. This campaign utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall amjadsamraIf 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 measure, you can avoid using the amjadsamra package and any other packages associated with the tea.xyz campaign. Additionally, you can monitor your package-lock.json file for any unauthorized changes or additions. Using tools like Vulert can help you identify vulnerabilities in your dependencies without requiring code access.
Conclusion
The amjadsamra package poses a significant risk due to its malicious code designed to exploit the npm registry. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to safeguard their projects against such vulnerabilities.
See every vulnerability recorded for amjadsamra →
FAQ
The amjadsamra package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code can lead to the pollution of the npm registry, potentially compromising the integrity of your project and affecting your reputation as a developer.
You should uninstall the amjadsamra package immediately using the command npm uninstall amjadsamra and check for any other potentially malicious packages.
Regularly update your packages to their latest versions and use tools like Vulert to monitor your dependencies for vulnerabilities.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can use the Vulert playground to check if your application is affected by this vulnerability without any signup.
