Malicious Code Injection in amjadjasem Package: npm Vulnerability Overview
Summary
MAL-2025-170846: Malicious code in amjadjasem (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 amjadjasem 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 altered metadata to inflate developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in the amjadjasem package originates from its involvement in the tea.xyz token reward campaign. This campaign utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to pollution of the npm registry, making it difficult for developers to trust the integrity of packages and potentially exposing them to further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall amjadjasemIf 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 amjadjasem package until a secure version is released. Additionally, consider using package-lock.json to monitor your dependencies for vulnerabilities. Tools like Vulert can help you identify if your application is affected by this vulnerability without requiring code access or installation.
Conclusion
The amjadjasem package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and users. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for amjadjasem →
FAQ
The amjadjasem package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm ecosystem.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust package integrity and potentially exposing your application to further security risks.
You should update the package to a patched version if available or remove it from your dependencies until a secure version is released.
Yes, Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
