Malicious Code Injection in amjadtaheem Package: npm Vulnerability Overview
Summary
MAL-2025-170875: Malicious code in amjadtaheem (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 amjadtaheem 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 aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards in the tea.xyz protocol. The presence of malicious scripts in this package poses significant risks to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in the amjadtaheem package originates from its association with the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the packages within the ecosystem. Developers using this package may unknowingly introduce malicious code into their applications, leading to potential security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall amjadtaheemIf 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 amjadtaheem package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The amjadtaheem package presents a significant security risk due to its malicious code injection capabilities. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for amjadtaheem →
FAQ
The amjadtaheem package is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the amjadtaheem package immediately and check for any dependencies that may be affected.
Yes, tools like Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
