Malicious Code Vulnerability in amjadkabeer Package
Summary
MAL-2025-170848: Malicious code in amjadkabeer (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 amjadkabeer 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 mechanisms. 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. This behavior poses a significant risk to developers and users relying on the integrity of npm packages.
Vulnerability Detail
The vulnerability originates from the amjadkabeer package being part of a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to trust the packages they use. This vulnerability can result in compromised applications, loss of reputation for developers, and potential security risks for end-users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall amjadkabeerIf 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 amjadkabeer package and replace it with a trusted alternative. Always verify the integrity of packages before including them in your project.
Conclusion
The amjadkabeer package poses a significant risk due to its malicious behavior of flooding the npm registry with untrustworthy packages. It is essential for developers to remove this package from their projects and to monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for amjadkabeer →
FAQ
The amjadkabeer package is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing mechanisms.
This vulnerability can lead to the pollution of the npm registry, making it difficult to trust the packages you use, and may compromise the security of your application.
You should uninstall the amjadkabeer package immediately using the command npm uninstall amjadkabeer.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.
Yes, you should look for well-maintained and widely used packages that serve the same purpose as amjadkabeer, ensuring they have a good reputation in the community.
